Re: [tlug] Re: [RFC] Outline of the fast HTTP talk

[Curt Sampson <cjs@example.com>]

On 2008-11-05 13:41 +0900 (Wed), Edward Middleton wrote:

> Does it make much sense having a single request distributing its
> processing across more then one core?

Depends on the request. But mongrel processes *all* requests in a
single Ruby process. Thus, if you have eight cores and are running only
mongrel, seven of those cores will be idle, no matter what the load on
your server.

>: I could understand this being useful for a CPU intensive task like
>image processing but for a web server this just seems to be extra
>overhead.

When you're using a CPU-intensive interpreted language such as Ruby and
handling hundreds of requests per second, being "just" a web server
becomes a CPU-intensive task.

> evented_mongrel[1] thin[2] and ebb[3] can handle multiple requests
> fine without the need for native thread support in Ruby.

Again, only on one core.

cjs
-- 
Curt Sampson       <cjs@example.com>        +81 90 7737 2974   
Mobile sites and software consulting: http://www.starling-software.com