4 ms·
A good VNC client should give you responsiveness on par of RDP. VNC tunnel through web socket to a client running in a browser window may push it to the annoyin
by derekzhouzhen 4y ago
A good VNC client should give you responsiveness on par of RDP. VNC tunnel through web socket to a client running in a browser window may push it to the annoying zone though.
- lostapathy 4y agoWhat’s a good vnc client and server that actually pulls this off? I’ve never had any luck with it either. At least not on Ubuntu.
- maicro 4y agoIt's a little specialist, and doesn't have Linux server/host functionality (and IIRC Mac is still in beta), but if you want to remotely connect to a Windows 10+ computer - Parsec works really well. I've used it at work to share access to a beefy desktop for running CAD (SolidWorks) and multimedia (mostly Adobe Premiere Pro/CC) software, without having to be at the computer - we use it from the local network, and from across the country, with fairly satisfying performance.
- derekzhouzhen 4y agoIf it is from linux to linux, I'll use xpra https://xpra.org/ https://xpra.org/
- hedora 4y agoTigerVNC
- koumoula 4y agofrom the abcdesktopio github repository tigervnc this project uses TigerVNC release 1.12.0 it starts the command Xvnc and then websockify python to convert TCP socket as WebSocket
- digitallyfree 4y agoVNC can have good performance over gig LAN using raw encoding. The issues occur when you add compression (hextile, tight, etc.) which does a good job cutting bandwidth but adds a ton of latency, which is the main reason your sessions feels slow. RDP does a great job of keeping the latency down. Note that I have never had a good experience using noVNC (the web-based solution used by this service) even over fast LAN - I think it's because of the additional overhead of the web browser. I personally use SPICE for VDI which performs decently over LAN, but is not as good as RDP over WAN with constrained bandwidth.