On Fri, 2011-07-22 at 10:30 -0400, John A. Sullivan III wrote: > On Fri, 2011-07-22 at 00:26 -0400, John A. Sullivan III wrote: > > I suppose I'll cover this one next as John Williams raised one of the > > issues. This is another Windows only issue. > > > > This issue has two categories. It is complicated by the packing problem > > because we can only run the Windows client now with sub-optimal packing > > but it was a problem before the corruption issue struck. > > > > Screen painting is just slower - not just a little slower - a lot > > slower. The typical anecdotal test I've been using is scrolling through > > my Evolution Inbox. Evolution has always seemed to have terrible > > graphics handling. I don't know what it does but it is always sluggish > > and awkward - thus an excellent test of how well we handle challenging > > graphics. > > > > Even under Linux on a LAN, scrolling is miserably slow. Shift down > > arrow and wait 1/4 second for a response. This is really annoying. > > However, in Windows, it is wait 1/2 to 3/4 seconds for a response. This > > takes it from annoying to dangerous as users wind up deleting or opening > > unintended emails, i.e., the hold the shift down arrow until they think > > they have highlighted the mails they want and then press enter. What > > they don't realize is that five more emails will be selected because of > > the delay between what they see and the key buffer. > > > <snip> > Ugh! Make that 2 to 3 seconds between down arrow and response!!!! > > I tried to resume a session I had suspended from Linux but it complained > about a mismatched color depth. I checked my Windows laptop and, > indeed, it was set to 16 bit color. I changed it to 32 bit color and > performance has gone through the floor - John > <snip> Hmm . . . more important information. It almost looks like the events are being buffered. For example, if I arrow and wait, arrow, wait, arrow, wait, arrow wait - each arrow takes about 2-3 seconds for a screen response. If I arrow, arrow, arrow, arrow, the first screen response takes 2-3 seconds, then, 2-3 seconds later, all the other arrow events are processed.
Are we disabling the Nagle algorithm on all the sockets we open? We should if we are not. Otherwise, we can see this kind of buffering effect. I don't know why that would cause such a change between 16 and 32 bit. Just a thought - John _______________________________________________ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
