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.
Levente
At work we use VAST and I have experience with VW as well and those
smalltaks react to my keyboard and mouse actions instantly. But Pharo
works very sluggish.
My image is about 130MB because I have loaded all dutch postcode in
memory, but that should not affect the performance of general
operations like typing with the keyboard. I am not a fast typer, but
sometimes it takes seconds to show my keyboard input. I can't use the
down key to select the right method from suggestions, because it seems
to lockup completely.
Are there ways to speedup Pharo? I would love to use cogVM but I
haven't got gemtools working on it...
Will upgrading to 1.1.1 fix these issues?
Is my OS (Windows 7-64bit) causing these issues?
Regards,
Bart
_______________________________________________
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
