Quote:
|
Originally Posted by tobor
Yeah, I'm running into a lot of problems just setting up a server to use Rails. Dispatch.fcgi runs around 20Megs in memory and lighttpd had a setting of max 5 to speed-up any rails request. It's recommended you don't run full production mode during development, but i just wanted to see how the environment reacted. Server stopped being able to execute any shell commands because no memory could be allocated (VPS with 256MB memory). This is the third serve we've tried. A lot of other servers that do support rails, only support early versions, which have some notable problems.
I'm going to save the rails development for another project, where we can get dedicated, and truly develop in our own environment.
|
pity, that's more than enough bang for a couple of mongrels etc.;could be a number of system things - if an extra 20-25mb is throwing a wobbly then you have other issues; that said, fcgi has again been consigned to the bin in favour of mongrel
Quote:
|
Originally Posted by Transmogrify
What do you mean by "rails is single threaded so uploads are blocking"?
|
single threaded applications control concurrency by allowing the process to obtain a mutex lock - blocking all other requests until the process has finished; uploads take significant time (even if it's just a few seconds) which will block your entire application until the upload is complete
every request is affected the same way, it's just noticeable with long running processes
this leads to the scaling model of adding further rails processes - what you're doing by having a pack of two mongrels - in order to handle concurrent requests
think ive posted this link before but here it is again anyway
Xen And The Art Of Rails Deployment » SlideSharemeh.