Hi all,
for Debian we have provided libjpeg-turbo on squeeze, wheezy and sid.
From my point of view it is indeed not necessary to recompile NX to
be used with libjpeg-turbo. People may correct me if that is not true.
So for a running X2Go server and client you can drop in
on squeeze: apt-get install libjpeg-turbo62
on wheezy, sid: apt-get install libjpeg-turbo8
And your host should then run with libjpeg-turbo instead of libjpeg.
Please note, that this change affects every application on that
system. So... no warranty given from our side. Also, if testing
libjpeg-turbo, please read the documentation of libjpeg-turbo:
http://code.x2go.org/gitweb?p=libjpeg-turbo.git;a=blob;f=README-turbo.txt;h=...
Happy testing + looking for feedback!!! Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi Mike, Am 29.01.2012 00:46, schrieb Mike Gabriel:
Hi all,
for Debian we have provided libjpeg-turbo on squeeze, wheezy and sid.
From my point of view it is indeed not necessary to recompile NX to be used with libjpeg-turbo. People may correct me if that is not true.
So for a running X2Go server and client you can drop in
on squeeze: apt-get install libjpeg-turbo62 on wheezy, sid: apt-get install libjpeg-turbo8
And your host should then run with libjpeg-turbo instead of libjpeg. Please note, that this change affects every application on that system. So... no warranty given from our side. Also, if testing libjpeg-turbo, please read the documentation of libjpeg-turbo: http://code.x2go.org/gitweb?p=libjpeg-turbo.git;a=blob;f=README-turbo.txt;h=...
It should be possible to use libjpeg-turbo only with nxproxy and x2goagent. If you specifying the directory where this libraries are installed in proxy and agent wrappers using the LD_LIBRARY_PATH environment variable. In that case it will not have affect on other applications in system.
Happy testing + looking for feedback!!! Mike
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Hi Alex,
On Mo 30 Jan 2012 14:01:02 CET Oleksandr Shneyder wrote:
And your host should then run with libjpeg-turbo instead of libjpeg. Please note, that this change affects every application on that system. So... no warranty given from our side. Also, if testing libjpeg-turbo, please read the documentation of libjpeg-turbo: http://code.x2go.org/gitweb?p=libjpeg-turbo.git;a=blob;f=README-turbo.txt;h=...
It should be possible to use libjpeg-turbo only with nxproxy and x2goagent. If you specifying the directory where this libraries are installed in proxy and agent wrappers using the LD_LIBRARY_PATH environment variable. In that case it will not have affect on other applications in system.
The fundamental question is if we want to offer libjpeg-turbo with
X2Go for distros that do not have libjpeg-turbo. If so, we could
install libjpeg-turbo into /usr/lib/nx/.
Shall we do this?
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 30.01.2012 14:50, schrieb Mike Gabriel:
Hi Alex,
On Mo 30 Jan 2012 14:01:02 CET Oleksandr Shneyder wrote:
And your host should then run with libjpeg-turbo instead of libjpeg. Please note, that this change affects every application on that system. So... no warranty given from our side. Also, if testing libjpeg-turbo, please read the documentation of libjpeg-turbo: http://code.x2go.org/gitweb?p=libjpeg-turbo.git;a=blob;f=README-turbo.txt;h=...
It should be possible to use libjpeg-turbo only with nxproxy and x2goagent. If you specifying the directory where this libraries are installed in proxy and agent wrappers using the LD_LIBRARY_PATH environment variable. In that case it will not have affect on other applications in system.
The fundamental question is if we want to offer libjpeg-turbo with X2Go for distros that do not have libjpeg-turbo. If so, we could install libjpeg-turbo into /usr/lib/nx/.
Shall we do this?
Mike
Hm, I'm not sure. I think, the users should be able to decide it. But we can make configuration of X2Go with libjpeg-turbo be easier. For example, if user have already installed libjpeg-turbo_1.1.90_i386.deb from http://sourceforge.net/projects/libjpeg-turbo/files/1.1.90%20%281.2beta1%29/ , agent wrapper can check if directory /opt/libjpeg-turbo/lib/ exists and export it to LD_LIBRARY_PATH. I'm not sure that we should provide libjpeg-turbo by ourself.
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Hi Alex,
On Mo 30 Jan 2012 15:11:51 CET Oleksandr Shneyder wrote:
Hm, I'm not sure. I think, the users should be able to decide it.
Yes, that's what I think, too. And, I also think the distro
maintainers should decide whether libjpeg-turbo is used on the distro
and also whether libjpeg is fully replaced by libjpeg-turbo or whether
libjpeg-turbo is an option for the distro users.
Unfortunately, Debian does not have libjpeg-turbo in SID yet.
But we can make configuration of X2Go with libjpeg-turbo be easier. For example, if user have already installed libjpeg-turbo_1.1.90_i386.deb from http://sourceforge.net/projects/libjpeg-turbo/files/1.1.90%20%281.2beta1%29/ , agent wrapper can check if directory /opt/libjpeg-turbo/lib/ exists and export it to LD_LIBRARY_PATH. I'm not sure that we should provide libjpeg-turbo by ourself.
I am not sure on this...
Currently, I think, offering the packages for Debian in the nightly
repositories should be all we do. People have a .deb based
installation source for the library (which we already do for Debian
squeeze, wheezy and sid) and once installed, people can use
dpkg-divert to select which JPEG lib they can use. As long as we do
not have proper test results and a proof that libjpeg-turbo is a great
enhancement, we should not customize X2Go to use it.
Once we have test results, the distros may already have incorporated
it in their archives and this discussion becomes pointless, anyway...
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 29.01.2012 00:46, schrieb Mike Gabriel:
From my point of view it is indeed not necessary to recompile NX to be used with libjpeg-turbo. People may correct me if that is not true.
So for a running X2Go server and client you can drop in
on squeeze: apt-get install libjpeg-turbo62 on wheezy, sid: apt-get install libjpeg-turbo8
And your host should then run with libjpeg-turbo instead of libjpeg. Please note, that this change affects every application on that system. So... no warranty given from our side. Also, if testing libjpeg-turbo, please read the documentation of libjpeg-turbo:
Guys,
it would be really helpful if someone could type up a step-by-step guide for testing. I'd love to try this out, but either I *did* something wrong or something *goes* wrong, as the following had no positive effect whatsoever:
The only effect I saw was a "screen hang" when leaving YouTube for another web site, and no speed increase whatsoever. :-(
Looking at the discussion in this thread and at the libjpeg-turbo documentation leaves me even more confused than before.
My questions, in particular, are: libjpeg-turbo - gain less speed than a fullscreen session - but that was
years ago and may have changed and may not apply to X2Go at all, I don't know.) 3) Is the library required on both the server *and* on the client? 4) Should it work "out of the box" after installing the package, or do I have to change some file somewhere to add the library path? 5) Do I have to restart a daemon after changing this file? 6) Why was I able to install the package without apt-get telling me it would remove the "non-turbo" library package? To make this clear, I don't complain about a lack of a warning (Mike did provide such a warning in his posting), but I'm surprised about the lack of *action* i.e. no library package has been removed when I installed the libjpeg-turbo62 package.
Kind Regards, Stefan
Hi Stefan,
On Mo 30 Jan 2012 18:37:40 CET "newsgroups.mail2@stefanbaur.de" wrote:
Am 29.01.2012 00:46, schrieb Mike Gabriel:
From my point of view it is indeed not necessary to recompile NX to
be used with libjpeg-turbo. People may correct me if that is not
true.So for a running X2Go server and client you can drop in
on squeeze: apt-get install libjpeg-turbo62 on wheezy, sid: apt-get install libjpeg-turbo8
And your host should then run with libjpeg-turbo instead of
libjpeg. Please note, that this change affects every application on
that system. So... no warranty given from our side. Also, if
testing libjpeg-turbo, please read the documentation of
libjpeg-turbo:Guys,
it would be really helpful if someone could type up a step-by-step
guide for testing.
I'd love to try this out, but either I *did* something wrong or
something *goes* wrong, as the following had no positive effect
whatsoever:
- add heuler repository, apt-get update
- apt-get install libjpeg-turbo62 on my squeeze-based server
- connect from latest Microsoft Windows client to said server
- use Iceweasel in rootless mode, access YouTube and watch a movie
What compression do you use? 16m-jpeg-9?
The only effect I saw was a "screen hang" when leaving YouTube for
another web site, and no speed increase whatsoever. :-(
hmmm...
- Will this currently only work between Linux Clients and Linux Servers?
jpeg compression is performed on both sides: client _and_ server, I
guess. It can have an effect on both sides (I guess).
- Will it work with rootless sessions? (I remember NoMachine/FreeNX
once stated that rootless sessions in general - i.e. not related to
libjpeg-turbo - gain less speed than a fullscreen session - but that
was years ago and may have changed and may not apply to X2Go at all,
I don't know.)
It should...
- Is the library required on both the server *and* on the client?
Best performance is achieved if it is installed on both: server and
client. But it can be installed on either, only.
- Should it work "out of the box" after installing the package, or
do I have to change some file somewhere to add the library path?
out-of-the-box, by theory... However, we should compare a drop-in of
the package into an already running server with an NX (redistributed)
compiled on a system where libjpeg-turbo is installed during package
build. Not sure if that changes performance gain...
- Do I have to restart a daemon after changing this file?
No daemons involved here, at all.
- Why was I able to install the package without apt-get telling me
it would remove the "non-turbo" library package? To make this clear,
I don't complain about a lack of a warning (Mike did provide such a
warning in his posting), but I'm surprised about the lack of
*action* i.e. no library package has been removed when I installed
the libjpeg-turbo62 package.
Please read more about dpkg-divert: http://www.debian-administration.org/articles/118
And refer to the postrm and preinst scripts of libjpeg-turbo: http://code.x2go.org/gitweb?p=libjpeg-turbo.git;a=tree;f=debian
Kind Regards, Stefan
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...