From: Jeff McNeil <jeff@...>
Date: 2005-10-01T09:10:56+09:00
Subject: Re: Threading Performance?

Yeah, a lot like pre-KSE FreeBSD threads, implemented via poll(). I'm  
not an expert in the area, but I believe a lot of user space  
threading libraries are implemented this way (people used to run some  
apps under a linked-in LinuxThreads as an alternative).

I can work around it using a different design approach, more in-tune  
with what Rick suggested.

-Jeff

On Sep 30, 2005, at 12:11 PM, Paul wrote:

> I've had similar experiences. As far as I remember from when we had a
> peek under the hood to check the thread implementation, its based on a
> select() model. Ruby threads are not really threads in the sense of
> scheduled time-sliced processes.
>
> In my case, we were writting something similar (HTTP decoding engine)
> and handled the network io with ruby threads (because that what  
> selects
> are really good for), but then handled decoding in a forked child
> (because its all CPU, it would have blocked the other ruby 'threads').
>
>
>