Issue #5621 has been updated by Mike Perham.


My use case: I want to use Rails in thread-safe mode in production so I don't have to fork 20 Ruby processes to handle 20 concurrent requests.  When developing, Rails auto loads classes on every request.  This auto loading is critical to Rails' rapid development cycle and there's no way I'm going to disable it.  Unfortunately the current autoload behavior makes the development environment incompatible with thread-safe mode.

Since no developer wants to lose the rapid development cycle and no developer is crazy enough to run a very different configuration in production than development (going from non-thread-safe to thread-safe between dev and prod is a huge change), no one currently uses thread-safe mode.

I will try trunk in a few days and report back if it solves the problem.
----------------------------------------
Backport #5621: Please backport thread-safe autoloading patch
http://redmine.ruby-lang.org/issues/5621

Author: Mike Perham
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


This is critical to using Rails in thread-safe mode.  JRuby is supposed to have it in the next release, 1.7.

http://redmine.ruby-lang.org/issues/921

Waiting another 12-18 months for 1.9.4 to come out would really suck.


-- 
http://redmine.ruby-lang.org