X2Go Bug report logs - #813
Performance drop using large virtual screen

version graph

Package: x2goserver; Maintainer for x2goserver is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goserver is src:x2goserver.

Reported by: Hrvoje Habjanić <hrvoje.habjanic@zg.ht.hr>

Date: Tue, 10 Mar 2015 15:15:01 UTC

Severity: normal

Found in version

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#813; Package x2goserver. (Tue, 10 Mar 2015 15:15:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Hrvoje Habjanić <hrvoje.habjanic@zg.ht.hr>:
New Bug report received and forwarded. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Tue, 10 Mar 2015 15:15:02 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.x2go.org (full text, mbox):

From: Hrvoje Habjanić <hrvoje.habjanic@zg.ht.hr>
To: submit@bugs.x2go.org
Subject: Performance drop using large virtual screen
Date: Tue, 10 Mar 2015 16:06:03 +0100
Package: x2goserver


I noticed that using large screens (bigger than 800x600) causes x2go to
start slowing down. Especially problematic are full-screen switches, for
example when you switch from one virtual screen to another, inside of
x2go virtual screen. This slow down is experienced as sudden session
freeze, depending on screen size, it can stall for up to few seconds.
After some time this becomes really annoying ...

This is not influenced by switching to different
encoding or line speed in GUI.

Eventually i did track down to cache sizes. In /usr/bin/x2gostartagent file
there is fixed cache size: "cache=8M,disk=32M".

Increasing this cache size completely removes this freeze, and also
significantly reduces session bandwidth! For example, with session
1680x1050, using 16bit RLE, changing cache to "64M" bandwidth drops
from 3-4Mbit/s down to ~200kbit/s! I also noticed better responsiveness
when using "disk=0".

So, it seems that default settings (cache=8M,disk=32M) are maybe too
small for todays use with lager virtual screens, and this should be
I would suggest using at least "cache=64M" as default.

Also, it would be nice to add a possibility to change those values in a nice
way, since directly editing the script is more like a hack. Also, when
script is
updated, changes are lost.



Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Tue Dec 18 10:52:41 2018; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.