On Oct 17, 2010, at 12:37 AM, Levente Uzonyi wrote: > On Sat, 16 Oct 2010, Bart Veenstra wrote: > >> Hi list, >> >> I have been working with Pharo for almost a month now, and I suspect >> that the performance is degrading fast. UI tasks takes several seconds >> to react to my keyboard. > > That kind of sluggishness is probably related to finalization/gc. Please send > us the result of the following expression: > > (WeakArray classPool at: #FinalizationDependents) > select: [ :each | each notNil ] > thenCollect: [ :each | each class -> each size ] > > There's another source of sluggishness though. The input is only processed at > every 10 milliseconds (actually more rarely, because there's at least 10 ms > delay between input processing). > If I evalute [InputEventPollingFetcher eventPollPeriod: 1], then Pharo 1.1 > feels more responsive. > Btw it would be better to use the input semaphore instead of polling for > events, like Squeak does it. I wonder why was it changed.
The idea was to remove the poll behavior now I do not remember if the semaphore was removed or simply was waiting for the windows vm to get the support and was forgotten. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
