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

On Wed, Aug 13, 2008 at 4:35 AM, SASADA Koichi <[e-mail]> wrote:
> Hi,
>
> Giuseppe Bilotta wrote:
>>
>> 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.
>
> I have no idea to achieve your issue.
>
> Seeing other environment:
>
> - Python: there is no priority on Thread.
> - Perl ithread: OS dependent priority.
>  (not affect on most UNIX environment)
>  (on Windows environment, we can use priority)
> - C, C++'s native thread: ditto.
>
> (Please point out if you find mistakes)
>
>
> There are 2 options:
>
> 1. This is Ruby's good point, so we must support
>   OS independent exact thread scheduler
>   (with development/running cost).
>
> 2. We don't need such big mechanism on thread because
>   other environments don't support it.
>
> (optional-3: we should choose 1 or 2 on build/launch timing)

The ideal solution would be to keep Thread#priority= and map it to the
appropriate system-level call (SetThreadPriority() on Windows [if Ruby
uses native threads there], nice() on Linux, etc). However, I have no
idea how complex this would be to implement.


-- 
Giuseppe "Oblomov" Bilotta