I guess my problem is that it appears that there is some sort of throttle on
this, somewhere. That is, why doesn't the client saturate my ISDN line with
screen updates, instead of a "steady" 3KB/sec fpr 3 full minutes? Why
doesn't it behave the same way over my internal ethernet? It's not like it
"knows" there is a slower connection involved (I don't think it does,
anyway). So, if it takes 3 minutes to update at 3KB/sec over an ISDN line,
why doesn't it take that long on a 10BaseT connection?
Also, using the RH system monitor, there was virtually NO CPU usage at all
during these extremely slow updates.
I believe we DID have the -C option as well, at least on one of the
experiments, and got the same behavior.
>If you can, run your window manager on the display, not the remote
>machine.
I believe the remote was connecting via Xterm from within an X session of
some sort, at least on Mandrake. THe other experiment was using WinAxeP on
a Winbox. Both exhibited this extreme sluggishness.
BW
> -----Original Message-----
> From: Dr Andrew C Aitchison [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, November 12, 2002 10:26 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Xpert]FW: Lots of IP traffic, no screen activity
>
> On Tue, 12 Nov 2002 [EMAIL PROTECTED] wrote:
>
> > > Not sure if this is the correct list, but I'll give it a try. We're
> > > trying to move from M$ to Linux, using Netraverse via X to diskless
> (or
> > > minimal - like a ThinkNic) workstations. We're in proof-of-concept
> mode
> > > here, and are trying to serve this up via the internet to a remote
> > > station. While this seems to work very speedily over my ethernet
> > > connection, it is horribly slow over an ISDN (here in Texas) ->T1
> > > connection (in Tennessee). Looking at the bandwidth, it is generally
> > > using about 3K bytes per second, but doing little to nothing on the
> remote
> > > screen. Screen refreshes that take a second or so locally are taking
> up
> > > to 3 MINUTES on the remote, with a constant 3K bytes/sec of traffic.
> > > Occasionally we see a burst of 10Kbytes/sec, but not often, and there
> > > appears to be no connection with that burst and the rate of screen
> > > refresh.
> > >
> > > The way we are doing this is:
> > >
> > > ssh -X -f user@localserver <application>
> > >
>
> Try adding the -C option to that ssh command.
> For images compressiong the data wont help, but for other stuff it might
> be a win.
> Note that on Linux some versions of ssh compression is disabled when
> privilege separation is enabled.
>
> If you can, run your window manager on the display, not the remote
> machine.
> If not go for a lightweight window manager.
>
> Also avoid fancy backgrounds and other image heavy applications.
>
> --
> Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
> [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna
>
> _______________________________________________
> Xpert mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xpert
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
