Hi,
Time and again i've realized that the if my ruby processes running
rails code were eating up memory and increasing consistently in mem-
size after every incoming http request, then it was post probably
because of the way it was coded. The post has some info on these
aspects:
http://www.engineyard.com/blog/2009/thats-not-a-memory-leak-its-bloat/
.
http://github.com/noahd1/oink was helpful when it came to checking
which actions result in what kind of increase in the memory usage.
It also seemed to be that the more routes my rails app had (typically
due to different kinds of nesting of resources) the bigger was the
size of the ruby processes.
If the code of your app seemed pretty much in control, then it might
be case that you are running it in development mode. I've seen that
switching the app to production mode can stabilizes the process size.