Miles to go …

Rails 2.2 is slated to become multi-threaded. What does it mean for JRuby users ? Charles Nutter explains it:

Q/A: What Thread-Safe Rails Means

One of the key points from the blog is:

Rails deployments on JRuby will use 1/Nth the amount of memory they use now, where N is the number of thread-unsafe Rails instances currently required to handle concurrent requests. Even compared to green-threaded implementations running thread-safe Rails, it willl likely use 1/Mth the memory where M is the number of cores, since it can parallelize happily across cores with only “one” instance.

NetBeans development and GlassFish deployment already provide an ideal environment for Rails deployment.

All previous entries in this series are archived at LOTD.

Technorati: lotd rubyonrails jruby ruby netbeans glassfish

1. LOTD #4: Rails running on GlassFish @ LinkedIn
2. LOTD #21: Production Deployment Tips for running Rails on GlassFish v2 using Windows
3. LOTD #9: Advantages of JRuby over MRI
4. LOTD #6: Rails Deployment on GlassFish in 4 steps and 15 minutes
5. LOTD #16: Hotspot Flags, JRuby Version String, and JRuby/MRI Benchmark