On Mon, 2010-06-28 at 09:30 +0200, Erik Auerswald wrote: > Hi, > > On Mon, Jun 28, 2010 at 06:55:56AM +0000, cougarmaster wrote: > > Was reading about how to increase SSH performance and I came across this. > > Would this help in speeding up X2GO in anyway are just a waste of time? > > I don't think SSH is the bottleneck for normal X2Go use. Usually the > network link between server and client has little bandwidth (think DSL or > cable modem) and can be easily saturated by standard openssh without any > tuning. Thus the client side would not profit significantly from the > changes in HPN-SSH. > > On the server side you start several SSH processes, thus getting the multi > thread functionality without a patch. There is no need to adjust the > internal SSH buffers either, because of the low bandwidth links to the > clients. > > What might help on a heavy loaded server or on slow clients (e.g. VIA > or ARM based thin clients without hardware AES encryption) would be the > use of the blowfish cipher. [Disclaimer: I did not check which cipher > is selected by X2Go.] > > > Also in there is a link to tuning network performance too just wanted > > to see if it would be of any help. > > This is the standard network performance tuning found everywhere. This is > interesting for a saturated server, but will not solve any fundamental > speed issues. > > Br, > Erik I have been wondering if it will help with resilience. We are having problems where, if the Internet connection starts dropping packets, recovery of the X2Go client is much slower than recovery of other applications such as web browsing. We have tried playing with ClientAliveInterval and ClientAliveCountMax but that has not helped. Has anyone else been able to make X2Go session more robust across poor quality connections? Thanks - John
_______________________________________________ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
