Bug 5812 - upgrade libjpeg-turbo to get SIMD accelerated huffman encoder/decoder
Summary: upgrade libjpeg-turbo to get SIMD accelerated huffman encoder/decoder
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Build system (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.8.0
Assignee: Henrik Andersson
URL:
Keywords: ossman_tester, relnotes, samuel_tester
Depends on:
Blocks: performance
  Show dependency tree / graph
 
Reported: 2016-03-01 12:35 CET by Pierre Ossman
Modified: 2017-03-20 17:09 CET (History)
3 users (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2016-03-01 12:35:33 CET 
The next release of libjpeg-turbo (1.5) will have aa SIMD accelerated huffman encoder and decoder, giving a claimed 10% improved performance. Code is already in place both for x86 and ARM.

We should upgrade so we can take advantage of this.
Comment 1 Henrik Andersson cendio 2016-11-21 13:21:44 CET 
Latest version of libjpeg turbo is 1.5.1
Comment 3 Pierre Ossman cendio 2016-11-24 13:31:47 CET 
Verified that chavez is properly updated.

Tested x86_64 client and server. Works well, although I'm not seeing any noticeable performance increase. It's not worse either though, so...
Comment 4 Pierre Ossman cendio 2016-11-24 16:22:02 CET 
Tested i686 client and server as well. Basically the same thing; it's difficult to see any difference. Perhaps a few percent less CPU usage.
Comment 5 Pierre Ossman cendio 2016-11-25 10:51:54 CET 
Tested Windows 10. No noticeable change there either.
Comment 6 Henrik Andersson cendio 2016-11-25 11:18:43 CET 
Tested both armel and armhf clients agains older server. There seems to be a drop in cpu load with about 10% between 4.7.0 client and build 5301 on both arm platforms but not sure if this is from the libjpeg upgrade.
Comment 7 Samuel Mannehed cendio 2016-11-25 11:25:13 CET 
Tested the client on MacOS 10.11. I compared build 5301 and the 4.7.0 release and I'm not seeing any differences in either CPU use or in perceived performance.
Comment 8 Samuel Mannehed cendio 2016-11-25 11:25:48 CET 
All done then.
Note You need to log in before you can comment on or make changes to this bug.