On May 30, 2009, at 19:00 , Henrik Sperre Johansen wrote: > On 30.05.2009 18:18, Stéphane Ducasse wrote: >> >> >>> I belive the "higherPerformance" preference can also be removed, the >>> only thing it does it is increase the max possible GUI fps from the >>> default 50 to 1000. >>> >> This is not that simple. Marcus told me that for server this is >> important since it can suck all cpu. >> > I believe we are in agreement, just using different words: > - Server mode: Gives 50ms between redraws for non-GUI activity. > - Normal mode: Gives (20ms - Time spent in last redraw) for non- > GUI activity. > - "higher"Performace: Gives (1ms - Time spent in last redraw) for > non-GUI activity. > > If there's no new damage rects, no redrawing happens in updateCycle. > For say, a server app with f.ex. a monitoring GUI which sends out > dmg rects once one of it's models values that are displayed in the > GUI changes, normal can be painful, and downright nasty with > higherPerformance enabled when it comes to time left to do actual > application stuff... (Especially if GUI contains complex elements, > damage rects are somewhat off, + a plethora of other things that > are, at the moment, quite likely). > > So server mode setting is a must-have, higherPerformance not much so.
Exactly. "Server Mode" is an important fix I added to solve the image freezing problem two years ago: http://bugs.squeak.org/view.php?id=6581 "Higher performance" can be removed. Cheers, Adrian > > > Cheers, > Henry > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
