Navneet Aron navneeta...@gmail.com wrote:
Hi Folks, I've a rails application in production environment.The rails app
has both a website as well as REST apis that are called by mobile
devices. It has a apache front end and 8 mongrel_rails running when I start
the cluster. Each of them
Hi Folks, I've a rails application in production environment.The rails app
has both a website as well as REST apis that are called by mobile
devices. It has a apache front end and 8 mongrel_rails running when I start
the cluster. Each of them stabalize around 60 MB initially. After that
pretty
200-300MB is not unusual for a rails application.
Is it growing past that?
Maybe use 3 or 4 mongrels, rather than 8.
On 22 Jul 2009, at 09:18, Navneet Aron wrote:
Hi Folks,
I've a rails application in production environment.The rails app
has both a website as well as REST apis that are
8 mongrels are way too much capacity. Do you need that many ? Mongrels
taking 300MB is not unheard of as James said. Are you using loads of
libraries or cache in memory ? Moreover counting per mongrel memory is not
so easy. If they use shared libraries the memory per process shoots up in
the ps
Piyush, James,Thanks for your replies.
1. The memory keeps increasing beyond 300MB and eventually the mongrel_rails
process goes away one by one.
2. I'm not doing any caching yet.
3. As you can see below, some processes use a lot of memory and evntually
die.
Here's a snapshot of ps auwx
root
Piyush == Piyush Ranjan piyush...@gmail.com writes:
Piyush 8 mongrels are way too much capacity. Do you need that many ?
Mongrels
Piyush taking 300MB is not unheard of as James said. Are you using loads of
Piyush libraries or cache in memory ? Moreover counting per mongrel memory
Navneet == Navneet Aron navneeta...@gmail.com writes:
Navneet Piyush, James,Thanks for your replies.
Navneet 1. The memory keeps increasing beyond 300MB and eventually the
mongrel_rails
Navneet process goes away one by one.
Check dmesg output.
You may be getting OOM killed. Do
