[Mongrel] Mongrel and memory usage
pete at nextengine.com
Mon Nov 5 11:22:28 EST 2007
Along the lines of Thomas question, I've noticed that my mongrel
rails processes start at around 50 MB, and creep up to around 100 MB
(or a little over) pretty soon after being used. Is this something
other folks are seeing (i.e. standard rails overhead), or does it
sound specific to my app?
Also, if anyone has any tips on finding memory leaks in mongrel,
they'd be much appreciated. I've played with watching the
ObjectSpace. Is this the best way?
Kirk: thanks for the tip on Array.shift with Ruby 1.8.5. I'll keep
an eye out for this.
On Nov 5, 2007, at 8:09 AM, Thomas Balthazar wrote:
> On 11/5/07, Alexey Verkhovsky <alexey.verkhovsky at gmail.com> wrote:
>> On 11/5/07, Kirk Haines <wyhaines at gmail.com> wrote:
>>> On 11/5/07, Thomas Balthazar <thomas.tmp at gmail.com> wrote:
>>>> I never see the two Mongrel processes memory footprint decrease.
>>>> Is it normal?
>>> Ruby is a garbage collected language. Ruby has a conservative mark
>>> and sweep garbage collector.
>> But Ruby processes never release memory back to the operating system.
>> So, the fact that its RSS never goes down is normal.
>> In normal circumstances, Mongrel should grow up to some point around
>> 60-120 Mb and stay there. 300 Mb and growing is a sure sign you
>> have a
>> memory leak somewhere.
>> Alexey Verkhovsky
>> CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]
>> RubyWorks [http://rubyworks.thoughtworks.com]
>> Mongrel-users mailing list
>> Mongrel-users at rubyforge.org
> Hello Alexey,
>> 300 Mb and growing is a sure sign you have a memory leak somewhere.
> What would you suggest me to investigate?
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
More information about the Mongrel-users