You really really do not want to just poke values in to these things trying to find something that seems to work.
There are a lot of reasons a device can be "laggy." Specifically in terms of RAM, this is usually a matter of how much paging the kernel needs to do as your running apps use their ram vs. how much background app processes are killed to reclaim memory for foreground apps.
On devices with a lot of RAM, this is not much of an issue, so the values (in particular the oom minfree values) are generally tuned conservatively to more aggressively kill background processes in order to avoid paging.
When you are getting tight on RAM, there is a careful balance between having enough RAM to keep everything running in the background the user may reasonably desire and avoiding paging.
Also the desired values for these vary with the type of device -- for example a device with a higher resolution screen needs more RAM for its frame buffers; one with a higher density screen needs more RAM for its widget graphics. These both increase the overall working set of the running system, requiring more RAM available to avoid paging.
The current values for these in the GB tree are tuned for a Nexus S style device -- a fair amount of RAM, hdpi phone screen. You can tune those down a bit for lower-end devices, but keep a careful eye on how much paging is happening.
Of course if your laginess is not related to paging, none of this will help.
--
Dianne Hackborn
Android framework engineer
hac...@android.comNote: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them.