 |
|
||
|
|
PasteUpMorph MinCycleLapse: |
In my quest to decrease the number of screen updates and/or reduce the amount of nework traffic moved the Disney folks were kind enought to point out an existing feature.
PasteUpMorph MinCycleLapse: 100
The default value is 20 and it controls morphic updates.
The end result of how it affects things is detailed below in a note I posted to the Squeak mailing list, how it really works requires some careful code reading.
My test morphic has two stars that chase each other in circles with some ramdom stepping.
For a normal case (1 minute or so) I got 1919 screen updates across 6,115,757 pixels, or about a 56 pixel square updated for each update. Now If I change MinCycleLapse to 250 then we get 1165 updates for 5,490,835 pixels, or a 69 pixel square.
Less updates and roughly the same amount
of data moved as Andreas pointed out, so win win.
{Andreas pointed out the number of updates should decrease and
the data moved stays the same}
Now for my deferred VM at 250 millisecond delay I get 247 updates, but it moves 16,669,139 pixels or a square of 260 pixels per update. More data, less updates.
The trade is data movement versus latency in doing the x-windows call for remote servers.
PS I'm going to validate that a 3.6 inch square is reasonable for my update and that it encompasses the two morphic that move... Seems larger, perhaps I've a bug...