3 ms·
It doesn't look like this has ANYTHING to do with Mongrel, Apache, or HTTP at all! He had ridiculous memory leaks from ActiveRecord/Rails under the older 'stab
by blasdel 17y ago
It doesn't look like this has ANYTHING to do with Mongrel, Apache, or HTTP at all!
He had ridiculous memory leaks from ActiveRecord/Rails under the older 'stable' version of Ruby he was using with Mongrel. When he switched to Passenger, which uses a patched/forked version of Ruby (the hilariously named "Ruby Enterprise Edition"), his Rails memory leak went away.
- blader 17y agoThis is correct. It's REE - mod_rails has almost nothing to do with these results. REE alone halved our response times and our memory usage across our Rails cluster. We're stll on mongrel/nginx.
- RobbieStats 17y agoPossibly, but wouldn't know without testing that. Still doesn't address the global queue issue.