That may be from the documentation, I'm not sure. Anyway, you're
right that it doesn't support SSL. Not sure why you'd need/want it
to. Mongrel, as far as I know, was developed from the ground up to be
a Rails server. If you need stuff like SSL, you use a web server that
supports SSL and uses mod_proxy to talk to Mongrel. Which it sounds
like you have in Apache
If you only have one Mongrel process, then yeah it'll choke on
multiple requests to slow-running pages. That certainly doesn't seem
like a fault of Mongrel though...any time you have a single thread of
access and really slow code you're going to have trouble.
Now for my experience...I've been running pregopoker.com for the past
6 months, and it's using Apache with mod_proxy to Mongrel. All the
static stuff is handled by Apache, as well as the SSL. I run it on
three mongrel processes, and it handles 80k requests/day with no
problem, the vast majority of them being handled by Mongrel. 80k
isn't even a request/second...I'm not going to get into detailed stats
and standard deviations like Zed wants, mainly cause I just don't care
Mongrel runs great for my config. I'd have to say that most pages
are relatively slow...each request results in some fairly complex math
going on in the background. I can almost assure you that all my pages
run slower than yours will, and I've never run into a problem with
Mongrel breaking down under heavy access.
Mongrel's also never crashed on me. Not once.
Long story short, Mongrel is not for kiddies. Mongrel is perfect for
hosting Rails apps, and runs great behind a full-featured webserver
for handling the other duties.