Hi, I am trying to deploy my application that requires rails-2.3.8, ferret_server running in background(DRB) and workling_client+sterling. Above configuration is running on a VPS with 512MB, latest Ruby Enterpise Edition+ passenger+nginx+mysql. But I continue to see out of memory issues. What I notice that every ruby thread is consuming 15%of 512MB(from top) including workling and ferret_server. Are there some ways to fine tune ruby, passenger or others to make sure that I do not run out of memory ? From REE documentation, it seems that ruby thread spawned by passenger can share rails environment and application code. Is it possible to do similar kind of sharing with passenger+ferret_server+workling, because it seems that each one of these is loading same code separately. What are the the other ways to reduce RAM requirement ? Any help will be appreciated. Thanks, np -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
> What are the the other ways to reduce RAM requirement ?You probably need to figure out what is eating all that RAM. memprof might help. -r -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
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. On Aug 31, 10:39 pm, rogerdpack <rogerpack2...@gmail.com> wrote:> > What are the the other ways to reduce RAM requirement ? > > You probably need to figure out what is eating all that RAM. > memprof might help. > -r-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.