April 21, 2012
10:37 p.m.
Sean P. DeNigris wrote
small -> 212 msec huge -> 1491 msec
I should've also mentioned: very large -> 232 msec huge, but code font at 18pt - 241 msec - **GCs**... incr 17 totalling 27ms (12.0% uptime), avg 2.0ms - 8.3% {19ms} NautilusWindow(Morph)>>fullBounds very large, but code font at 24pt - 1551 msec - **GCs**... incr 174 totalling 383ms (25.0% uptime), avg 2.0ms - 59.5% {923ms} NautilusWindow(Morph)>>doLayoutIn: So having a "huge" i.e. 24pt code font is definitely one of the issues... -- View this message in context: http://forum.world.st/Unresponsive-1-4-image-tp4574693p4577286.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.