From: Mark Somerville Date: 2011-05-10T08:53:58+09:00 Subject: [ruby-core:36076] [Ruby 1.9 - Feature #3436] Spawn the timer thread lazily Issue #3436 has been updated by Mark Somerville. I'm repeating what I said in another thread to catch people that have subscribed to this bug. Suraj Kurapati wrote: > It seems Mark was the only person to review (()). > > What do the other Ruby developers think about it? > > Will it not be committed because it lacks Windows support? > > Thanks for your consideration. With the 1.9.2 release schedule now public and rather imminent, now is the time to get this tested and reviewed. I really think this regression should be fixed for 1.9.3 - if you do too, please help make it happen! ---------------------------------------- Feature #3436: Spawn the timer thread lazily http://redmine.ruby-lang.org/issues/3436 Author: Maximilian Gass Status: Open Priority: Normal Assignee: Category: Target version: =begin As discussed in http://redmine.ruby-lang.org/issues/show/1820, Ruby 1.9.1 always spawns a timer thread which is required to handle scheduling of Ruby threads. Rubinius did the same and I suggested to only spawn the thread if it is required, only when Ruby threading is used. I don't know anything about the internals of Ruby, but could this method be used in MRI as well? The timer thread prevents the CPU from going idle and saving power/battery, so it would be nice to avoid it. =end -- http://redmine.ruby-lang.org