RDP-backend is too slow / uses too much network bandwidth
Weston/RDP could be ideal for a personal use case of mine, running a headless remote desktop server on my workstation that I could then access from home, over an SSH tunnel. (It is very important to use an SSH tunnel and restrict access to the RDP server ports, because there does not seem to be any client authentication.)
When I tried it, it was unusably slow even with a relatively small desktop over a 1.0/0.5 MB/s link. Dragging a window results in a slow motion movie where the window goes through all the intermediate positions instead of skipping to the final position, for instance.
I hear the RDP-backend implementation is kind of naive. It could be a lot smarter in making the most out of the available network bandwidth.
@rdp.effort, could you list here some things to implement in the RDP-backend that would improve the performance?
How much does the RDP client software affect this, what would you recommend? I tried with Remmina, and I recall Vinagre was even worse.
I cannot work on this myself, but I'd like people to know that the slowness is not inherent to Wayland or even to pixel-based remoting schemes, and that there are things one could do to make it better.