I just wanted to experiment with an event driven scheduler and see if it 
makes any kind of difference in performance, especially in the case of many 
concurrent processes.


>From: Bert Freudenberg <bert at freudenbergs.de>
>Reply-To: The general-purpose Squeak developers 
>list<squeak-dev at lists.squeakfoundation.org>
>To: The general-purpose Squeak developers 
>list<squeak-dev at lists.squeakfoundation.org>
>Subject: Re: Alternative Thread Schedulers
>Date: Tue, 29 May 2007 21:10:00 +0200
>
>
>On May 29, 2007, at 20:28 , J J wrote:
>
>>Hi all,
>>
>>I just read http://wiki.squeak.org/squeak/5682 that Tim (I think it  was) 
>>mentioned, and found the part about doing alternative  scheduling with a 
>>higher priority thread interesting.
>>
>>The question I had was, in the example it says the high priority  process 
>>can use Delay's to sleep while other processes are running,  but what 
>>happens when a process does IO?  Doesn't that cause the  process to yield?
>>
>>What I am thinking is, if I were to make a scheduler process that  manages 
>>all running processes, how can he find out every situation  where a 
>>process yields in some way?  It would be ideal if there was  a Delay 
>>millisecondsOrUntilInterupt: type message.
>
>What's the actual problem you want to solve with your alternative  
>scheduler?
>
>- Bert -
>
>
>

_________________________________________________________________
PC Magazine’s 2007 editors’ choice for best Web mail—award-winning Windows 
Live Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507