NeverBlock Unleashed

After months of development and meticulous hard work, NeverBlock is finally in production, having been deployed on eSpace's very own MeOwns.com. NeverBlock allows memory usage to decrease by 75%, while capacity for concurrent requests has been effectively doubled. This allows sites that utilize NeverBlock to increase their capacity for handling concurrent requests, while at the same time reducing memory requirements significantly. We also spent some time fixing the subtle MySQL connection issues that happened with long running requests. The result of the work is a more polished and solid NeverBlock that has been running smoothly on MeOwns.com for a while now, which increases our level of confidence in the library and makes us believe that NeverBlock is now ready for prime time.

Comments

1.

Congratulations guys! Great job! We're planning to deploy it soon also!

2.

Congratulations! I've been looking at NeverBlock for awhile now and it looks really awesome. Good job. I'm just wondering how this works with Rails 2.2. Isn't Rails 2.2 now thread safe so is there still a need for NeverBlock? I'm no expert on thread safety so I'd love it if you could help clarify what your project offers over say, mongrel and Rails 2.2 with thread safety turned on. Thanks, and again, congratulations!

3.

Where are the official docs that describe using this with Rails?

4.

@Paul, Integration work for Rails 2.2 is not done yet. If you really need to scale your IO then you should consider using NeverBlock with Ruby 1.9.1. @Alex, please refer to this blog post: http://www.espace.com.eg/neverblock/blog/2008/09/04/neverblock-instant-scaling-for-your-rails-apps/