---------- Forwarded message --------- From: Ulrich Sibiller <uli42@gmx.de> Date: Sun, May 31, 2020 at 10:58 PM Subject: Re: [ArcticaProject/nx-libs] Document compression (#802) To: ArcticaProject/nx-libs <reply+ABQHBZHBGIOEJSNWVCG4BAV4372CLEVBNHHBUM3YJI@reply.github.com> Cc: ArcticaProject/nx-libs <nx-libs@noreply.github.com>, Author <author@noreply.github.com>
"nopack" in x2go becomes "none" in NX. And it means exactly what it says: do not compress images. This setting saves CPU cycles but required more bandwidth. Images are normally cached this so this is relevant only for the tiem an image must be transferred to the other side.
All the things I documented are valid for plain NX sessions (without using x2go but other software). In NX - if you don't specify a compression method explicitly but only a link type - the compression method is derived from the link type. For ADSL you correctly expect adaptive-7 as I listed in the document.
Using x2go things are a bit different. The NX code is the same and so are the built-in defaults. For ADSL this is still "adaptive-7". But x2go does always provide a compression type in addition to the link type. So that default is never used but overridden by the compression settings the user specifies in x2go's session configuration. So regarding compression you always get what you select there, in your case it is "nopack" (which becomes "none" at some point because of the internal naming of the parameter).
In other words: in x2go you always have to select a clever combination of link speed and compression while using plain NX you can stick with the link speed and use the defaults.
If you only touch the link speed setting you will always get 16m-jpeg.
I am using an own software for connection (which I cannot make public for legal reasons) and always stick with the defaults. I was not aware of this x2go behaviour. But this might explain why I don't see the performance problems I sometimes hear about from other people.
So I consider this a bug.
Developers: what's your opinion about this?
Uli
On Sun, May 31, 2020 at 10:27 PM Anton Driesse <notifications@github.com> wrote:
Sorry, you lost me.
I think you're saying nopack is the same as "no pack", but did you say what nopack really is?
Anyway, using nopack I do observe that the choice of link makes a difference.
ADSL gave me reasonable update speed and quality; with MODEM I expected quick update and poor quality, but I got slow update and poor quality; with LAN I expected and got slow update but high quality.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Am 31.05.20 um 23:14 schrieb Ulrich Sibiller:
In other words: in x2go you always have to select a clever combination of link speed and compression while using plain NX you can stick with the link speed and use the defaults.
If you only touch the link speed setting you will always get 16m-jpeg.
I am using an own software for connection (which I cannot make public for legal reasons) and always stick with the defaults. I was not aware of this x2go behaviour. But this might explain why I don't see the performance problems I sometimes hear about from other people.
So I consider this a bug.
Developers: what's your opinion about this?
Not a developer, but as the community manager, I would like to throw in my 0.02€ here as well:
To me, this sounds like we should either change the value of the compression setting to a new default when the slider is moved by the user, or display a "recommended compression setting" next to it.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On Sun, May 31, 2020 at 11:35 PM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
To me, this sounds like we should either change the value of the compression setting to a new default when the slider is moved by the user, or display a "recommended compression setting" next to it.
I think, x2go should make specifiying the compression optional and rely on the built-in defaults otherwise. This means not specifiying compression in the nx options file if the user has not exlicitly selected a compression.
For existing session configurations I don't see a way to distinguish if the user selected the compression on purpose or not if the compression is 16m-jpeg-9.
Uli
Hello together,
did we have nightly opsi packages for x2goclient? Or maybe portable version of it, like https://portableapps.com/apps ? I think it's primary interesting for windows people. I know /S option for Windows Installer and howto install X2Go Client without admin rights. But it's not the same.
Best Regards, Juri Grabowski
Am 02.06.20 um 14:27 schrieb x2go-dev@jugra.de:
Hello together,
did we have nightly opsi packages for x2goclient? Or maybe portable version of it, like https://portableapps.com/apps ? I think it's primary interesting for windows people. I know /S option for Windows Installer and howto install X2Go Client without admin rights. But it's not the same.
Nothing official. I did package the stable client in the past, though: <https://github.com/bauritcs/opsi-bauritcs/tree/master/x2goclient-bitcs>
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
Am 31.05.20 um 23:39 schrieb Ulrich Sibiller:
For existing session configurations I don't see a way to distinguish if the user selected the compression on purpose or not if the compression is 16m-jpeg-9.
Aaand that's why the client should display a recommendation next to the compression field. See my point now?
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On Tue, Jun 2, 2020 at 3:59 PM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 31.05.20 um 23:39 schrieb Ulrich Sibiller:
For existing session configurations I don't see a way to distinguish if the user selected the compression on purpose or not if the compression is 16m-jpeg-9.
Aaand that's why the client should display a recommendation next to the compression field. See my point now?
Yes and no. For new sessions I'd prefer a cleaner configuration window where you can decide to use the defaults. For existing sessions we could display "this session is not using the recommend default" and ask the user if that's on purpose.
Uli
Am 02.06.20 um 16:10 schrieb Ulrich Sibiller:
On Tue, Jun 2, 2020 at 3:59 PM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 31.05.20 um 23:39 schrieb Ulrich Sibiller:
For existing session configurations I don't see a way to distinguish if the user selected the compression on purpose or not if the compression is 16m-jpeg-9.
Aaand that's why the client should display a recommendation next to the compression field. See my point now?
Yes and no. For new sessions I'd prefer a cleaner configuration window where you can decide to use the defaults. For existing sessions we could display "this session is not using the recommend default" and ask the user if that's on purpose.
For a new session, we would set the default in the field, and when the user manually changes it, they will be presented with the same notice they would see when making changes to an existing session, or when going to the tab to review their settings, when their setting doesn't match the default. We could also consider logging a warning or notice in the text box during session startup.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On Tue, Jun 2, 2020 at 4:48 PM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 02.06.20 um 16:10 schrieb Ulrich Sibiller:
On Tue, Jun 2, 2020 at 3:59 PM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 31.05.20 um 23:39 schrieb Ulrich Sibiller:
For existing session configurations I don't see a way to distinguish if the user selected the compression on purpose or not if the compression is 16m-jpeg-9.
Aaand that's why the client should display a recommendation next to the compression field. See my point now?
Yes and no. For new sessions I'd prefer a cleaner configuration window where you can decide to use the defaults. For existing sessions we could display "this session is not using the recommend default" and ask the user if that's on purpose.
For a new session, we would set the default in the field, and when the user manually changes it, they will be presented with the same notice they would see when making changes to an existing session, or when going to the tab to review their settings, when their setting doesn't match the default. We could also consider logging a warning or notice in the text box during session startup.
I would like to have the compression settings to be grayed out until the user explicitly activates them. Selecting a certain link speed could still update the compression specific GUI elements to the respective defaults of the selected link speed. As soon as the user activates the compression settings this GUI element updates will no longer happen. In addition the defaults of the selected link speed could be displayed.
Uli
-
Stefan Baur -
Ulrich Sibiller -
Ulrich Sibiller -
x2go-dev＠jugra.de