Here's another possibility that I encountered before I was smarter (heh)
Are you providing download capabilities of large files. I manage a
support site for firmware downloads and other documents. Before I
discovered the X-Sendfile header, mongrel was loading and serving the
files. I had MAJOR memory spikes. Now that Apache is grabbing that
request (and sending the file) before proxying the request to Mongrel,
no more problems.
matte - webmonkey
[EMAIL PROTECTED]
Benjamin Krause wrote:
Fernando,
I am using mongrel for a long time... But just now I see a problem.
I am running 3 instances using mongrel_cluster and nginx as a
reverse proxy. When I start the cluster I have a memory usage of
20MB per instance... In the end of the day this usage is something
about 230MB for each instance. It should be a memory leak?
This is most probably a memory leak, but not necessarily a mongrel
related issue.
You should check your app with bleak_house[1] or any other memory
profiling tool to see, where the leak comes from. I had the same
problem and the leak was caused by ferret[2]. Some native extensions
(like rmagick) might be the problem.
Ben
[1] http://blog.evanweaver.com/files/doc/fauna/bleak_house/files/
README.html
[2] http://blog.omdb-beta.org/2007/7/29/tracking-down-a-memory-leak-
in-ferret-0-11-4
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
