We're seeing that all the time with our Rails apps. I'm looking at
four processes right now in the 700 to 900MB range.
My first guess is that it's something in Rails or our app. After all,
that's where most of the code is. You might try running requests
through WEBrick on a test server to see if the leak still occurs. If
so, then you know at least part of it is Rails.
There's always nightly restarts ;) Not my choice on how to do things,
but hey, it'll have to hold till I can fix bigger things.
What's the Ruby GC like? Circular references a problem?
Thomas Balthazar wrote:
Hello,
I'm running a Rails application which must sort and manipulate a lot
of data which are loaded in memory.
The Rails app runs on 2 mongrel processes.
When I first load the app, both are 32Mb in memory.
After some days, both are between 200Mb and 300Mb.
My question is : is there some kind of garbage collector in Mongrel?
I never see the two Mongrel processes memory footprint decrease.
Is it normal?
I use Mongrel 1.0.1 with Rails 1.2.3 on Debian.
Best regards,
Thomas.
------------------------------------------------------------------------
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
begin:vcard
fn:Robert Mela
n:Mela;Robert
email;internet:[EMAIL PROTECTED]
x-mozilla-html:FALSE
version:2.1
end:vcard
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
