Steve, Have you checked the memory usage of the server when it gets into this state? It's also worth checking the Windows event logs to see if there are any tell-tale errors from core OS components or drivers around the time the problem occurs. Finally, you can also check the number of handles that processes are holding via the Task Manager, which may help you determine whether it's a resource issue.
Regards, -- Wez @ RealVNC Ltd > -----Original Message----- > From: vnc-list-ad...@realvnc.com [mailto:vnc-list-ad...@realvnc.com] On > Behalf Of steve l > Sent: 12 February 2009 13:42 > To: vnc-list@realvnc.com > Subject: Screen updates go slow after 2 weeks > > Hi all, > > I'm running VNC server 4.1.2 on a win2k server and have found that > screen > updates start to happen very slowly after having the server up for > around 2 > weeks. I'm making fairly heavy use of VNC (I'm connected to the server > for > at least 4hrs per day). Any suggestions on how I can troubleshoot > this? > Some observations so far.... > > - Its not a gradual performance degradation - the server goes straight > from > working fine to taking around 5-20s to update the screen - it's like > something breaks. > - This has happened 3 times so far and the system seems to fail after > (roughly) the same period of time. > - The delay only seems to occur on certain events...moving the mouse, > dragging windows, updating of counters/graphs within windows seems OK. > Changing the window focus (e.g. alt-tab) is a problem. > - Some of the time, the window gets partially drawn (usually the border > and > toolbars), then it freezes and the rest gets drawn (equally quickly) > after > the freeze. > - Not everything gets delayed - if I have Windows Task Manager set to > 'always on top' with the performance graphs showing & I change the > window > focus from one application to another, I see the borders of the new > application get drawn, the window then sits there for around 10s and > the > rest of the detail then gets filled in. Meanwhile, the task manager > graphs > have continued to scroll/update throughout. > - The system remains 99% idle throughout the freeze. I don't see the > CPU > utilization go up and the winvnc4.exe process doesn't appear to grab > any > more cycles. > - Pings from the client to the server remain at 1-2ms throughout the > freeze. > - The slow response remains regardless of which client machine or VNC > client > I connect from (i've tried realvnc and tightvnc clients on windows and > linux > hosts). > - Restarting the VNC server process on the server doesn't help. > - Raising the priority of the VNC server process doesn't help. > - So far, rebooting the Win2k server is the only way I've been able to > fix > the problem. > > Cheers, > > Steve. > _______________________________________________ > VNC-List mailing list > VNC-List@realvnc.com > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
