From: Luc Heinrich <lucsky@...>
Date: 2001-12-20T06:51:18+09:00
Subject: [ruby-talk:28997] Re: A Ruby programmer walked into a bar and	ordered a Ruby-Thread

On 19/12/2001 21:54, "Dave Thomas" <Dave@PragmaticProgrammer.com> wrote:

> The interpreter is not thread safe, and the consensus seems to be that
> making it so would be a waste of time, given the upcoming rewrite. A
> secondary issue is the extensions that are already out there. How many
> of there are also not thread safe, and what impact would running under
> a native threading model have on them?

A pretty complex problem, indedd.

Now here is something related which bugs me, since I really don't know the
Ruby guts that much: would the Ruby threads, in their current incarnation,
scale as expected on a multiprocessor machine ? Would multiple Ruby threads
be correctly distributed on the multiple processors, or would they be stuck
(as I suspect them to) on the same precessor with the Ruby interpreter
process, since they are in-process ?

This would be yet another unfortunate but expected behavior, right ?

-- 
Luc - lucsky@mac.com