Intentional performance limitation?

Raab, Andreas Andreas.Raab at disney.com
Sat Feb 17 04:04:38 UTC 2001


Adrian,

The two are unrelated. The preference in the VM menu is actually outdated
for the latest images (it simply doesn't make any difference) but kept there
for people using older images.

Cheers,
  - Andreas

> -----Original Message-----
> From: Adrian Sampaleanu [mailto:AdrianS at mgisoft.com]
> Sent: Friday, February 16, 2001 1:09 PM
> To: 'squeak at cs.uiuc.edu'
> Cc: recipient list not shown
> Subject: RE: Intentional performance limitation?
> 
> 
> 
>   Thanks for the explanation Bob. Would you be able to also 
> tell me how this
> preference setting is related to the option on the F2 menu 
> that is called
> "Reduce CPU usage"? It would seem that setting the higher performance
> setting in the preferences window should unset the option in 
> the F2 menu,
> no? Or are they totally unrelated?
> 
>  Thanks again,
>  Adrian
> 
>  
> > Adrian,
> > 
> > Yes, the frame rate is limited intentionally. This is in 
> > order to reduce cpu usage in cases where the user would like 
> > other applications to be getting a fair (or larger) share of 
> > of the processor. The limit is around 50 fps which many feel 
> > is sufficient. The color picker, however, takes over some of 
> > this and forces extra displays to give more immediate 
> > feedback. If you would like to experiment with removing the 
> > frame rate limitation, go to the performance section of 
> > preferences and turn on higher performance. Note: there are 
> > problems with this -
> > 
> > - It hogs the cpu
> > - It messes up MVC big time
> > - The color picker is a bit harder to use in morphic
> > 
> > But I have it on all the time.
> > 
> > Cheers,
> > Bob
> > 
> 





More information about the Squeak-dev mailing list