> Thin doesn't use Mongrel [...] Rack is not a non-blocking concurrent library. Well, Thin uses mongrel's parser. Which makes it a sort of a library. And by co

> Thin doesn't use Mongrel [...] Rack is not a non-blocking concurrent library. Well, Thin uses mongrel's parser. Which makes it a sort of a library. And by concurrent I actually meant thread-safe. But forget it. The main point is: I cannot get any more better / optimal cpu usage with passenger (although I'm certainly getting some cpu / memory overhead). My single thin instance loads every single cpu core to 100% when attacked by httperf. And I was never able to crash it, although I probably didn't do my best. Monitoring and managing tools are okay, though monit and munin have been here for ages and I sort of like what they're capable of. But I still agree that ease of use is important for making ruby/rails even simpler and funnier to do. Whatever, no offense intended.