Hi Waldek,
cross-posting to x2go-dev ML as we should not SPAM the x2go-user list
with such complex stuff ;-) Maybe you want to subscribe to x2go-dev?
On Sa 21 Jan 2012 12:59:46 CET Waldek wrote:
Hi,
Anybody try to configure for example ubutu to configure x2goserver
to use libjpeg-tubro (
http://sourceforge.net/projects/libjpeg-turbo/ ) instead libjpeg ? I
have read that for example OpenNX client for neatx or freenx server
recommend to use this because libjpeg-turbo have speed improvement
than standard libjpeg and it will be use full to reduce transfer for
x2go session. I don't know how to configure (or is it possible?)
x2goserver on ubutu to use libjpeg-turboRegards
libjpeg-turbo support (from my perspective) is a distribution issue.
Libjpeg-turbo is pending for Debian sid inclusion:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341
As we do not have plans to ship libjpeg-turbo within the X2Go
repository currently, I guess we will have to wait for distro
inclusion in Debian/Ubuntu.
With other distros that already have libjpeg8 (optionally) replaced by
libjpeg-turbo, it should be possible to compile NX (redistributed)
against the faster libary.
There also is another NX related project on git.ethersoft.ru that
provides NX with libjpeg-turbo. However, that repos only builds NX for
FreeNX.
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...
Hi again,
On Mo 23 Jan 2012 18:57:37 CET Mike Gabriel wrote:
Hi Waldek,
cross-posting to x2go-dev ML as we should not SPAM the x2go-user
list with such complex stuff ;-) Maybe you want to subscribe to
x2go-dev?On Sa 21 Jan 2012 12:59:46 CET Waldek wrote:
Hi,
Anybody try to configure for example ubutu to configure x2goserver
to use libjpeg-tubro (
http://sourceforge.net/projects/libjpeg-turbo/ ) instead libjpeg ?
I have read that for example OpenNX client for neatx or freenx
server recommend to use this because libjpeg-turbo have speed
improvement than standard libjpeg and it will be use full to
reduce transfer for x2go session. I don't know how to configure
(or is it possible?) x2goserver on ubutu to use libjpeg-turboRegards
libjpeg-turbo support (from my perspective) is a distribution issue.
Libjpeg-turbo is pending for Debian sid inclusion: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341As we do not have plans to ship libjpeg-turbo within the X2Go
repository currently, I guess we will have to wait for distro
inclusion in Debian/Ubuntu.With other distros that already have libjpeg8 (optionally) replaced
by libjpeg-turbo, it should be possible to compile NX
(redistributed) against the faster libary.There also is another NX related project on git.ethersoft.ru that
provides NX with libjpeg-turbo. However, that repos only builds NX
for FreeNX.
I have just tested an NX build against libjpeg-turbo. The
libjpeg-turbo libraries I obtained from here:
http://people.debian.org/~fabo/libjpeg-turbo_1.1.90+svn704-1/
The test system was a Debian squeeze (so backporting from some brand
new SID package is possible).
When using 16m-jpeg-9 compression over a UMTS (HDSPA) uplink the
difference between libjpeg and libjpeg-turbo is smashing!!! It becomes
so much smoother...
From my perspective, we should start testing on nx-libs with
libjpeg-turbo in the nightly repository in the very very very near
future.
The change-over is easy: if libjpeg-turbo62 is installable in the
build chroot, NX builds against that one. If it is not present, it
builds against libjpeg62.
@Developers: please give feedback on the proposed step.
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...
Hi once again,
On Mo 23 Jan 2012 20:37:18 CET Mike Gabriel wrote:
Hi again,
On Mo 23 Jan 2012 18:57:37 CET Mike Gabriel wrote:
Anybody try to configure for example ubutu to configure x2goserver
to use libjpeg-tubro (
http://sourceforge.net/projects/libjpeg-turbo/ ) instead libjpeg ?
I have read that for example OpenNX client for neatx or freenx
server recommend to use this because libjpeg-turbo have speed
improvement than standard libjpeg and it will be use full to
reduce transfer for x2go session. I don't know how to configure
(or is it possible?) x2goserver on ubutu to use libjpeg-turboRegards
libjpeg-turbo support (from my perspective) is a distribution
issue. Libjpeg-turbo is pending for Debian sid inclusion: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341As we do not have plans to ship libjpeg-turbo within the X2Go
repository currently, I guess we will have to wait for distro
inclusion in Debian/Ubuntu.With other distros that already have libjpeg8 (optionally) replaced
by libjpeg-turbo, it should be possible to compile NX
(redistributed) against the faster libary.There also is another NX related project on git.ethersoft.ru that
provides NX with libjpeg-turbo. However, that repos only builds NX
for FreeNX.I have just tested an NX build against libjpeg-turbo. The
libjpeg-turbo libraries I obtained from here: http://people.debian.org/~fabo/libjpeg-turbo_1.1.90+svn704-1/The test system was a Debian squeeze (so backporting from some brand
new SID package is possible).When using 16m-jpeg-9 compression over a UMTS (HDSPA) uplink the
difference between libjpeg and libjpeg-turbo is smashing!!! It
becomes so much smoother...From my perspective, we should start testing on nx-libs with
libjpeg-turbo in the nightly repository in the very very very near
future.The change-over is easy: if libjpeg-turbo62 is installable in the
build chroot, NX builds against that one. If it is not present, it
builds against libjpeg62.@Developers: please give feedback on the proposed step.
Here is a recipe how to test NX with libjpeg-turbo:
ON SERVER
Install libjpeg-turbo from X2Go heuler repository (Debian-only)
apt-get build-dep nx-libs apt-get source -b nx-libs
(still on server) cd .. dpkg -i *.deb
ON CLIENT
Install your self-built packages libxcomp3 and nxproxy also on client
Happy testing
The above should work with Debian squeeze, wheezy and sid as test
system (amd64/i386).
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...
On Di, Jan 24, 2012 at 00:15:26 (CET), Mike Gabriel wrote:
Hi once again,
On Mo 23 Jan 2012 20:37:18 CET Mike Gabriel wrote:
Hi again,
On Mo 23 Jan 2012 18:57:37 CET Mike Gabriel wrote:
Anybody try to configure for example ubutu to configure x2goserver to use libjpeg-tubro ( http://sourceforge.net/projects/libjpeg-turbo/ ) instead libjpeg ? I have read that for example OpenNX client for neatx or freenx server recommend to use this because libjpeg-turbo have speed improvement than standard libjpeg and it will be use full to reduce transfer for x2go session. I don't know how to configure (or is it possible?) x2goserver on ubutu to use libjpeg-turbo
Regards
libjpeg-turbo support (from my perspective) is a distribution issue. Libjpeg-turbo is pending for Debian sid inclusion: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341
As we do not have plans to ship libjpeg-turbo within the X2Go repository currently, I guess we will have to wait for distro inclusion in Debian/Ubuntu.
With other distros that already have libjpeg8 (optionally) replaced by libjpeg-turbo, it should be possible to compile NX (redistributed) against the faster libary.
There also is another NX related project on git.ethersoft.ru that provides NX with libjpeg-turbo. However, that repos only builds NX for FreeNX.
I have just tested an NX build against libjpeg-turbo. The libjpeg-turbo libraries I obtained from here: http://people.debian.org/~fabo/libjpeg-turbo_1.1.90+svn704-1/
The test system was a Debian squeeze (so backporting from some brand new SID package is possible).
When using 16m-jpeg-9 compression over a UMTS (HDSPA) uplink the difference between libjpeg and libjpeg-turbo is smashing!!! It becomes so much smoother...
From my perspective, we should start testing on nx-libs with libjpeg-turbo in the nightly repository in the very very very near future.
The change-over is easy: if libjpeg-turbo62 is installable in the build chroot, NX builds against that one. If it is not present, it builds against libjpeg62.
@Developers: please give feedback on the proposed step.
Here is a recipe how to test NX with libjpeg-turbo:
ON SERVER
- Install libjpeg-turbo from X2Go heuler repository (Debian-only)
Won't that step replace the 'normal' system libjpeg? Are you sure that this step won't break existing applications?
These bug threads make me a bit nervous:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602034
Cheers, Reinhard
-- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4
Hi Reinhard,
On Di 24 Jan 2012 09:26:57 CET Reinhard Tartler wrote:
On Di, Jan 24, 2012 at 00:15:26 (CET), Mike Gabriel wrote:
Hi once again,
On Mo 23 Jan 2012 20:37:18 CET Mike Gabriel wrote:
Hi again,
On Mo 23 Jan 2012 18:57:37 CET Mike Gabriel wrote:
Anybody try to configure for example ubutu to configure x2goserver to use libjpeg-tubro ( http://sourceforge.net/projects/libjpeg-turbo/ ) instead libjpeg ? I have read that for example OpenNX client for neatx or freenx server recommend to use this because libjpeg-turbo have speed improvement than standard libjpeg and it will be use full to reduce transfer for x2go session. I don't know how to configure (or is it possible?) x2goserver on ubutu to use libjpeg-turbo
Regards
libjpeg-turbo support (from my perspective) is a distribution issue. Libjpeg-turbo is pending for Debian sid inclusion: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341
As we do not have plans to ship libjpeg-turbo within the X2Go repository currently, I guess we will have to wait for distro inclusion in Debian/Ubuntu.
With other distros that already have libjpeg8 (optionally) replaced by libjpeg-turbo, it should be possible to compile NX (redistributed) against the faster libary.
There also is another NX related project on git.ethersoft.ru that provides NX with libjpeg-turbo. However, that repos only builds NX for FreeNX.
I have just tested an NX build against libjpeg-turbo. The libjpeg-turbo libraries I obtained from here: http://people.debian.org/~fabo/libjpeg-turbo_1.1.90+svn704-1/
The test system was a Debian squeeze (so backporting from some brand new SID package is possible).
When using 16m-jpeg-9 compression over a UMTS (HDSPA) uplink the difference between libjpeg and libjpeg-turbo is smashing!!! It becomes so much smoother...
From my perspective, we should start testing on nx-libs with libjpeg-turbo in the nightly repository in the very very very near future.
The change-over is easy: if libjpeg-turbo62 is installable in the build chroot, NX builds against that one. If it is not present, it builds against libjpeg62.
@Developers: please give feedback on the proposed step.
Here is a recipe how to test NX with libjpeg-turbo:
ON SERVER
- Install libjpeg-turbo from X2Go heuler repository (Debian-only)
Won't that step replace the 'normal' system libjpeg? Are you sure that this step won't break existing applications?
These bug threads make me a bit nervous:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602034
I am not even sure if you can replace the libs on-the-fly (i.e.
without rebuilding NX). The libjpeg-turbo source package does not
provide a -dev package. It uses libjpeg-dev as installed with
libjpeg62-dev. Not sure if this is a mistake by Fabo (the guy you
prepared the package for Debian).
Only thing I can report is a change in speed and no obvious problems
with other apps.
There also has been developed a mature 8.0 emulation mode that still
has to be enable in the package. I may take a look at that later.
But basically, I think: yes, if the user installs libjpeg-turbo it
will have an effect on all applications.
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...
Those bug threads actually make me *less* nervous. The first one explains that libjpeg-turbo is just a derivative of standard libjpeg that uses SIMD instructions to accelerate functionality by 2-4x. The second mentions that there have been improvements to libjpeg-turbo to make it ABI-compatible with libjpeg8.
Looking at the readme ( http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/trunk/README-t...) on the (still active) sourceforge project shows that by default it is API/ABI compatible with libjpeg v6b, which is what is currently most widely used. It can also be configured to be compatible with v7 or v8 instead, but there are a few v7+ features that are not supported.
--
- Ben S.
On Tue, Jan 24, 2012 at 12:26 AM, Reinhard Tartler <siretart@tauware.de>wrote:
On Di, Jan 24, 2012 at 00:15:26 (CET), Mike Gabriel wrote:
Hi once again,
On Mo 23 Jan 2012 20:37:18 CET Mike Gabriel wrote:
Hi again,
On Mo 23 Jan 2012 18:57:37 CET Mike Gabriel wrote:
Anybody try to configure for example ubutu to configure x2goserver to use libjpeg-tubro ( http://sourceforge.net/projects/libjpeg-turbo/ ) instead libjpeg ? I have read that for example OpenNX client for neatx or freenx server recommend to use this because libjpeg-turbo have speed improvement than standard libjpeg and it will be use full to reduce transfer for x2go session. I don't know how to configure (or is it possible?) x2goserver on ubutu to use libjpeg-turbo
Regards
libjpeg-turbo support (from my perspective) is a distribution issue. Libjpeg-turbo is pending for Debian sid inclusion: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341
As we do not have plans to ship libjpeg-turbo within the X2Go repository currently, I guess we will have to wait for distro inclusion in Debian/Ubuntu.
With other distros that already have libjpeg8 (optionally) replaced by libjpeg-turbo, it should be possible to compile NX (redistributed) against the faster libary.
There also is another NX related project on git.ethersoft.ru that provides NX with libjpeg-turbo. However, that repos only builds NX for FreeNX.
I have just tested an NX build against libjpeg-turbo. The libjpeg-turbo libraries I obtained from here: http://people.debian.org/~fabo/libjpeg-turbo_1.1.90+svn704-1/<http://people.debian.org/%7Efabo/libjpeg-turbo_1.1.90+svn704-1/>
The test system was a Debian squeeze (so backporting from some brand new SID package is possible).
When using 16m-jpeg-9 compression over a UMTS (HDSPA) uplink the difference between libjpeg and libjpeg-turbo is smashing!!! It becomes so much smoother...
From my perspective, we should start testing on nx-libs with libjpeg-turbo in the nightly repository in the very very very near future.
The change-over is easy: if libjpeg-turbo62 is installable in the build chroot, NX builds against that one. If it is not present, it builds against libjpeg62.
@Developers: please give feedback on the proposed step.
Here is a recipe how to test NX with libjpeg-turbo:
ON SERVER
- Install libjpeg-turbo from X2Go heuler repository (Debian-only)
Won't that step replace the 'normal' system libjpeg? Are you sure that this step won't break existing applications?
These bug threads make me a bit nervous:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602034
Cheers, Reinhard
-- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Hi Ben, hi Reinhard,
On Di 24 Jan 2012 16:42:09 CET Benjamin Shadwick wrote:
Those bug threads actually make me *less* nervous. The first one explains that libjpeg-turbo is just a derivative of standard libjpeg that uses SIMD instructions to accelerate functionality by 2-4x. The second mentions that there have been improvements to libjpeg-turbo to make it ABI-compatible with libjpeg8.
Looking at the readme ( http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/trunk/README-t...) on the (still active) sourceforge project shows that by default it is API/ABI compatible with libjpeg v6b, which is what is currently most widely used. It can also be configured to be compatible with v7 or v8 instead, but there are a few v7+ features that are not supported.
--
- Ben S.
after some more reading I must say I (at least by theory) agree with
Benjamin. It is rather simple to enable libjpeg v8 emulation in
libjpeg-turbo. So for squeeze, I will leave 6b emulation mode in our
package, and for wheezy+ I enable v8 emulation and build new packages.
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...
On Tue, Jan 24, 2012 at 9:04 AM, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
after some more reading I must say I (at least by theory) agree with Benjamin. It is rather simple to enable libjpeg v8 emulation in libjpeg-turbo. So for squeeze, I will leave 6b emulation mode in our package, and for wheezy+ I enable v8 emulation and build new packages.
How does one enable "v8 emulation" for libjpeg-turbo?
I've been using x2go on Archlinux, and Arch uses libjpeg-turbo by default. I have not noticed any specific x2go problems that I can attribute to libjpeg-turbo, but I have been plagued by a lot of issues that I have assumed were due to x2goclient, but perhaps not all of them are the client's fault.
John,
The readme I linked explains how to do it. Basically, you have to re-run the configure script and re-build the library from source to produce a v7 or v8 ABI-compatible version.
On Tue, Jan 24, 2012 at 9:53 AM, John Williams <jwilliams4200@gmail.com>wrote:
On Tue, Jan 24, 2012 at 9:04 AM, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
after some more reading I must say I (at least by theory) agree with Benjamin. It is rather simple to enable libjpeg v8 emulation in libjpeg-turbo. So for squeeze, I will leave 6b emulation mode in our package, and for wheezy+ I enable v8 emulation and build new packages.
How does one enable "v8 emulation" for libjpeg-turbo?
I've been using x2go on Archlinux, and Arch uses libjpeg-turbo by default. I have not noticed any specific x2go problems that I can attribute to libjpeg-turbo, but I have been plagued by a lot of issues that I have assumed were due to x2goclient, but perhaps not all of them are the client's fault.
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
--
- Ben S.
On Tue, Jan 24, 2012 at 12:24 PM, Benjamin Shadwick <benshadwick@gmail.com> wrote:
The readme I linked explains how to do it. Basically, you have to re-run the configure script and re-build the library from source to produce a v7 or v8 ABI-compatible version.
Thank you. Here is the relevant section of the readme that you linked to:
By passing an argument of --with-jpeg7 or --with-jpeg8 to configure, or an argument of -DWITH_JPEG7=1 or -DWITH_JPEG8=1 to cmake, you can build a version of libjpeg-turbo that emulates the libjpeg v7 or v8 API/ABI, so that programs that are built against libjpeg v7 or v8 can be run with libjpeg-turbo.
Hi
Thank you very much for try use libjpeg-turbo with x2go and I hop it will be useful for many users
I will try tests on my ubuntu where I have access via UMTS on which is very useful any possibility optimization compression X Session
Regards
Waldek
2012/1/23 Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
I have just tested an NX build against libjpeg-turbo. The libjpeg-turbo libraries I obtained from here: http://people.debian.org/~**fabo/libjpeg-turbo_1.1.90+**svn704-1/<http://people.debian.org/%7Efabo/libjpeg-turbo_1.1.90+svn704-1/>
The test system was a Debian squeeze (so backporting from some brand new SID package is possible).
When using 16m-jpeg-9 compression over a UMTS (HDSPA) uplink the difference between libjpeg and libjpeg-turbo is smashing!!! It becomes so much smoother...
From my perspective, we should start testing on nx-libs with libjpeg-turbo in the nightly repository in the very very very near future.
The change-over is easy: if libjpeg-turbo62 is installable in the build chroot, NX builds against that one. If it is not present, it builds against libjpeg62.
@Developers: please give feedback on the proposed step.
Greets, Mike
-
Benjamin Shadwick -
John Williams -
Mike Gabriel -
Reinhard Tartler -
Waldemar Ogonowski