[#18121] [Ruby 1.8.7 - Bug #405] (Open) ssl.rb:31: [BUG] Bus Error — Anonymous <redmine@...>

Issue #405 has been reported by Anonymous.

14 messages 2008/08/04

[#18130] Re: New array methods cycle, choice, shuffle (plus bug in cycle) — Brian Candler <B.Candler@...>

> Seriously though... Array.first is a noun.

10 messages 2008/08/05

[#18319] NEW Command: absolute_path() -- — "C.E. Thornton" <admin@...>

Core,

14 messages 2008/08/16
[#18321] Re: NEW Command: absolute_path() -- — Yukihiro Matsumoto <matz@...> 2008/08/18

Hi,

[#18381] [Bug #496] DRb.start_service(nil) is very slow — Hongli Lai <redmine@...>

Bug #496: DRb.start_service(nil) is very slow

11 messages 2008/08/25

[ruby-core:18252] Re: result for mget [last:10 MIME/multipart] (1/1) (ruby-core ML)

From: "Giuseppe Bilotta" <giuseppe.bilotta@...>
Date: 2008-08-12 21:42:10 UTC
List: ruby-core #18252
>> We are planning to make Thread#priority(=) method as obsolete method
>> from Ruby 1.9.x.  This is due to implimentation/practical (maybe no
>> one use it) reason.
>
>> Any comments?
>
> Some way to reduce thread priority is important for situations like
> idling work-stealing threads in a nonblocking/lockfree way, which is a
> situation I've come up against recently.

I agree with this. I'm not sure if querying for the current priority
is widely used, but I work on at least one project where it's
necessary to set some intensive threads to a lower priorty to prevent
them from gobbling up too much CPU from the main threads, and not
having some way to reduce thread priority would be of noticeable
impact on our code.

-- 
Giuseppe "Oblomov" Bilotta

In This Thread

Prev Next