On 18 Nov 2009, at 08:46, Phoenix Rising wrote: > Yeah I'm using top to measure resource usage. I'll reboot a server > (virtual server of course), and at boot time memory usage is maybe > ~200mb. After a few days it's skyrocketed to consume all 2GB in the > case of the smaller application server we tested (haven't messed with > the other one since it's a public-facing application). What am I > doing wrong here?
Sounds to me like Passenger is spawning a lot more Rails instances than you presume. We've had a similar problem in the past, where we had to fix our code because of a Passenger conflict with a thread proxy. Since we are using Mongrel in development, we didn't notice until production apps started consuming all memory on the server within days. This was the one that gaves us trouble, but there's a few others as well: http://www.modrails.com/documentation/Users%20guide.html#_smart_spawning_gotcha_2_the_need_to_revive_threads Best regards Peter De Berdt -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=.
