If anyone cares, here's the results of my little experiment. setup: - application: authentication (RESTful authentication plugin on Rails VS auth-core on Merb) and file uploads (attachment_fu on Rails VS basic file uploads on Merb) - server running on my machine (2.13GHz Pentium M, 2.0 GB, Ubuntu Linux) - clients running on: localhost, 2 other Linux machines, 3 other PC machines (total 6 clients all running on the local network) - all clients start approximately at the same time and upload files (64KB or 1MB) to the server application - mongrel runs behind Apache with mod_proxy
--average client upload time in seconds-- setup 64KB 1MB 1 mongrel Rails 2.20 3.24 3 mongrel Rails 0.70 1.96 1 mongrel Merb 1.85 2.23 3 mongrel Merb 0.15 0.15 9 mongrel Merb 0.18 0.18 Tiberiu On Feb 23, 3:43 pm, Mr_Tibs <[email protected]> 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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
