![]() I can replicate a well-defined test and post a test from my system. Extra points if you can use simplescreenrecorder to record it, and then post it somewhere. To quote from my original post "connecting via xtightvnc over ssh" I'm connecting to a ubuntu server.Ī test scenario that demonstrates the abysmal performance. How are you starting the VNC server? (I don't think it matters, but for completeness.) RasPiOS Bullseye - Have tried with buster but it's also useless. I might try TigerVNC - it s at least good to know someone else has something workable - but I'd like to find out what the issue with xtightvnc and the 400 is. I can move windows around and the system keeps up with no apparent lag. I fired up my TightVNC client running against a TigerVNC server on RasPiOS Bullseye in a 2540x1350 window, and the performance is quite good. I haven't done any testing to compare Tiger and TightVNC, but my sense is that they are similar. I run virtual VNC servers of a few different screen sizes, using TigerVNC. You could try reverting from mutter to openbox and disabling the new mode-setting driver. Maybe this is a consequence of recent changes to the video system. I'm using wired ethernet, connected to the same port I had the Pi3 on.Īny suggestions welcome, but let me be 100% clear, it's VNC CLIENT performance that's the problem. Other network operations seem to work at the speed I expect. However after booting up my brand new 400 & doing the usual steps to get things up to date and using the exact same VNC config as I use on the Pi3, the VNC performance is glacial - like you move the mouse, and you can see the mouse pointer being redawn line by line, then it moves a bit & is redrawn line by line again as it slowly makes its way across the screen - it's completely unusable. Recently I decided to improve things by upgrading to a pi 400, so that I can do more memory & CPU intensive stuff locally, but the primary function is still to VNC into work. VNC performance is excellent - just like accessing a local device. ![]() I've been using a Pi3 for my WFH workstation, connecting via xtightvnc over ssh.
0 Comments
Leave a Reply. |