Mike Zornek on 15 Jan 2007 00:46:54 -0000 |
My company site is a rails app. Lots of pages are pretty plain, but I do run a custom blog, some basic contact forms, and some automated content stuff. http://clickablebliss.com/ Anyways, over the last few weeks I've watched as the 2 mongrel processes that power the site grow in memory footprint to the point where they'll chock my server and everything will die. It's strange cause I haven't done any real architectural changes and activity is not at it's peak. (Oct 2006 was clearly by busiest month) so I'm really sure why this is happening. I've started playing around with this memory profiler but haven't noticed what might be leaking just yet: http://scottstuff.net/blog/articles/2006/08/17/memory-leak-profiling-with-ra ils I also hope to be more aggressive with caching to avoid hitting the rails stack at all. (though I'm running into another issues where I can't get Apache to serve the cached rss feed with a application/xml mime type, which some readers will barf on). Overall, has anyone else run into memory leaking before and how did you work to find/fix it? FYI, the stack I use is pretty much the default one I get with Rails machine: http://railsmachine.com/solutions Thanks for you help/suggestions. ~ Mike -- Clickable Bliss, makers of: Billable: Simple Service and Invoice Tracking http://clickablebliss.com/billable _______________________________________________ To unsubscribe or change your settings, visit: http://lists.phillyonrails.org/mailman/listinfo/talk
|
|