[Pharo-project] Clue about morphic performance??

Gary Chambers gazzaguru2 at btinternet.com
Mon Feb 22 10:16:32 EST 2010

Indeed. Since Dolphin uses native window components, RDP can work at a more 
abstract level (i.e. aware of things like buttons, checkboxes etc.). So, for 
example, a button is drawn by the RDP client, effectively.

Squeak/Pharo draws its own, therefore all updates are bitmap based and the 
graphics (the World bits) are sent across the link...

Regards, Gary

----- Original Message ----- 
From: "Schwab,Wilhelm K" <bschwab at anest.ufl.edu>
To: <Pharo-project at lists.gforge.inria.fr>
Sent: Monday, February 22, 2010 12:28 PM
Subject: [Pharo-project] Clue about morphic performance??

> Hello all,
> I sometimes have reason to run code on machines that are accessible only 
> by a remote desktop connection, and I have noticed something that might be 
> a useful clue: on an identical setup (same server, same network, same RDP 
> client), Dolphin performs quite well and Pharo struggles (often severely). 
> Are we simply that much slower in generating graphics and/or pushing it 
> over the RDP connection, or is morphic drawing too much?  I suppose the 
> RDP server could be hindering Pharo by always sending one whole window 
> (e.g. the whole Pharo desktop) at a time or something stupid like that. 
> It might be worth a look by someone with morphic and RDP expertise.
> Bill
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 

More information about the Pharo-dev mailing list