Re:Production Rails Tuning with Passenger: PassengerMaxProce...
by jeremyw on Tuesday December 08, 2009 @02:51PM
(#984464)
If you're CPU-bound, you can't have greater throughput, by definition. Once you calculate your non-cpu latency (50% in my example) ceil(1/latency%) is your limit per core, before you start wasting resources.
Re:Production Rails Tuning with Passenger: PassengerMaxProce...
by jnewland on Tuesday December 08, 2009 @03:25PM
(#984541)
You can't gain any more cycles, of course, but you can gain throughput by adding processes to an already cpu-bound app by giving faster incoming requests a place to go instead of sitting on the global queue while waiting for other requests to process.
Having additional Passenger processes available even when CPU bound will allow for greater throughput (if at a less-than-ideal speed) than having requests back up on the queue, however - especially if those requests spend a good amount of time waiting on DB, memcached, or other external API calls.