[cw-discuss] Office2003 running on remote Xvnc causes extremely large X traffic

[Francois Gouget]

Hi,

Nikita V. Youshchenko wrote:
[...]
> Any hints why there is such huge X traffic, and how to avoid it?

I don't have a definitive answer to the first question. All I can say is 
that Windows applications are not designed for remote displays, simply 
because that's not possible on Windows (I believe that even Terminal 
Server Edition and the likes have a local frame buffer). So they may do 
'stupid' things like assuming GetPixel() and PutPixel() are cheap (the 
Windows Solitaire is known for that for instance). That's one factor, 
and the second one may be Wine's lack of a proper DIB engine (for the 
specialists).

The workaround would be to run the Windows applications on the same 
machine as the VNC server (in addition to allowing faster communication 
with the X server, it should also enable X's shared memory extensions 
which should decrease the traffic a bit). We've found that this usually 
works pretty well.

Regards,

-- 
Francois Gouget
fgouget at codeweavers.com