I am trying to do some rough math: Assuming 100ms per page, that's about 10 requests per second. With 8 mongrels per cpu (based on suggestions on the web), that's 80 requests per second.
This seems like a very low request/second per machine. How are people getting 1000 or so requests per second? Is my math wrong? What the average overhead by mongrel for cpu and ram? Thank you. On Apr 13, 9:26 am, Andy Jeffries <[email protected]> wrote: > On 13 April 2010 14:19, skarayan <[email protected]> wrote: > > > My understanding is that: > > 1. rails is single threaded and serves one request at a time > > 2. mongrel is single threaded and can process one rails request at a > > time > > 3. mongrel_cluster starts a few mongrel servers on the same machine > > > Based on this, the single most important factor becomes the time it > > takes to load a single page (to avoid blocking). > > Agreed. Consider Passenger though (as it's easier to manage than Mongrels) > or JRuby if you want multi-threaded serving. > > > If this is all true, what's considered a "good" page loading time? > > That's a "How long is a piece of string" type of question. I'd say aim for > 50-100ms, but it absolutely depends on what you're doing. As long as the > speed of page load given the amount of servers and traffic you have is > acceptable for your users then don't worry about it. > > Benchmark, measure, improve/accept rather than ask for opinions - it really > is the only way. > > Cheers, > > Andy -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
