[Pharo-project] Waste of CPU Power by polling events?
gstepken at googlemail.com
Mon Nov 22 22:08:31 CET 2010
I am just porting squeak/Etoys to Samsung-PAD and i noticed some strange
In Pharo 1.1 network connections seemed to be limited to 4 connections:
In the listenLoop backlogSize is set to 4. Means - Pharo is limited to
max. of four simultaneous TCP Connections?
But: Some MacIntel VM seem to run Squeak with additional worker thread
for event processing. Maybe this limitation may not occur here?
Carbon ports of Pharo use ioPeekKeystroke, ioGetKeystroke, ioMousePoint,
ioGetButtonState instead of
kEventRawKeyModifiersChanged and kEventMouseMoved event
Found in Pharo so far:
Hmmm ... quite a lot of events being polled:
I fear, that this costs a lot of wasted VM Power by polling. UNIX,
especially Linux is changing towards a event machine, driven by
interrupts. So - Interpreters should also migrated from polling to
interrupt driven event-machines.
I am missing that in Pharo. Pharo still has too much polling
code/algorithm running, that slows down Pharo/Squeak/Etoys ...
Any ideas appreciated ...
More information about the Pharo-project