Your own test seems to bear that out a full fledged computer running Windows 7 doesn't seem to be affected by the problem so that leads me to believe that the problem is with the dumb terminals themselves. That being said I've seen enough cases with dumb terminal performance to know that dumb terminals often don't have the horse power to provide a well performing session. RDP sessions (in my opinion) are much more sensitive to network issues such as lateny, congestion, and packet loss than they are to almost any other resource issue (memory, CPU, etc). Performance issues like you're describing are almost always (in my experience) network related. Is it as simple as the Wyse hardware not being able to redraw any faster? I don't have a more powerful Wyse device to compare with.
None of this has made even a small difference in the redraw rate.
I've tried disabling compression, USB/serial/sound, and pretty graphics (font smoothing, backgrounds, window dragging, etc.). However, on the thin-clients the redraw rate is much lower and there's a big difference. I don't believe the poor screen redraw rate has anything to with the host itself.įrom my Win 7 machines using Remote Desktop Connection I get a fairly decent redraw rate that does not leave me feeling uncomfortable or annoyed. It's a virtual machine and it has enough horsepower to handle the client load. I have Wyse V10L and C10L clients connected to a Server 2008 R2 host. I'm not interested in video playback or CAD/graphical performance. I've been reading about generally increasing the performance of an RDP session here but those posts don't seem to cover what I'm looking for which is specifically the redraw rate of windows.
0 kommentar(er)
