20425-Yield-longer-in-ProcessorScheduleridleProcess #444
Conversation
|
@estebanlm another try.. |
tesonep
changed the title
The work of the idle process is to run when no other smalltalk process is runnable. And the process will use a primitive to yield execution for a given amount of microseconds. The VM will either pick the closest delay to expire or the timeout provided and yield execution. It will resume earlier in case of I/O. Pick 50ms as this is the time WorldState will update in server mode. In the future we can increase it to minutes.
zecke
force-pushed
the
20425-Yield-longer-in-ProcessorScheduleridleProcess
branch
from
5651cd1
to
0b0d12d
Compare
|
@estebanlm I rebased it again. Any luck in trying to get it integrated? |
|
I have to say that I tested it myself and it seems to work fine (and eats a lot less processor), so I like this change. |
|
it maybe has a reason why is hardcoded? |
|
The evolution of this routine should be to vanish/call a "yield" primitive. The first goal is to just raise it a lot higher (as a safeguard, your VM would come back...). The Windows VM seems to have a race condition across wakeups but nobody cared on the ML. :( |
|
failing tests not related, I will accept this PR monday (to have time to rollback if something goes bad) |
|
let's hope it does not explodes :) |
The work of the idle process is to run when no other smalltalk process is
runnable. And the process will use a primitive to yield execution for a given
amount of microseconds. The VM will either pick the closest delay to expire
or the timeout provided and yield execution. It will resume earlier in case of
I/O.
Pick 50ms as this is the time WorldState will update in server mode. In the
future we can increase it to minutes.