About slugginess of 3.8 unstable

danielv at tx.technion.ac.il danielv at tx.technion.ac.il
Tue Oct 5 01:43:35 UTC 2004


So, real time tests would still be valuable. They give information now, and
can be replaced to use CPU time if that becomes available. 

About making the Squeak scheduler note CPU time - wouldn't it be
possible to do this from the image side, by calling the OS "CPU time for
process" at every Squeak process rescheduling?

Then it doesn't change VM performance, it can be turned on for profiling
and off again. Heck, if the call is cheap enough (no idea) compared to
Squeak scheduling, it might be worth leaving on.

Daniel

Stephan Rudlof <sr at evolgo.de> wrote:
> Interesting, too, could be a CPU running time for *each* Smalltalk
> process: but how to realize without compromising VM performance? Or
> wouldn't this be an issue?
> 
> 
> Greetings
> Stephan
> 
> > ...



More information about the Squeak-dev mailing list