On Feb 23, 2009, at 3:43 PM, Mr_Tibs wrote:
>
> Hi,
>
> I'm trying to stress test a scalable file-upload merb app. When I
> start the merb cluster, each merb worker process is about 1MB memory
> (btw, I start it with "merb -c 9"). My merb cluster is behind Apache +
> mod_proxy, so requests get distributed.
> I have 6 different clients (same network, Linux&PC) and they
> continuously upload 1MB file to the merb app. Almost immediately after
> they start pounding the merb app, the merb worker processes go from
> 1MB to 32MB of memory and they stay there.
> Why is this happening? I'm only using authentication and file upload.
> Are there memory leaks in any of these modules?
>
> Thanks,
> Tiberiu
Mr Tibs-
What you observe is pretty normal for merb apps. Each worker process
will use around 30Mb or so on average. The reason they start at 2mb
is that they are forks of the master, so they share memory. But ruby;s
garbage collector is not so smart and once you start running requests
through the workers they will bloat up to full size and no longer
share memory.
Cheers-
Ezra Zygmuntowicz
[email protected]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
