Latest revision as of 11:47, 2 July 2010

Replace libjpeg by libjpeg-turbo

Summary

libjpeg-turbo is fork of the original libjpeg project. It contains numerous performance related enhancements and is at least twice faster in JPEG compression/decompression than original libjpeg on platforms with MMX/SSE instruction set. It has same API/ABI like original libjpeg and also runs on non-SSE platforms where is around 25% faster.

Owner

Name: Adam Tkac

Current status

Targeted release: Fedora 14
Last updated: 2010-07-02
Percentage of completion: 100%

Detailed Description

Everything is written in summary.

Benefit to Fedora

Much faster JPEG compression/decompression library. JPEG codec is widely used and it is good to speed up core library which implements it. Additionally, libjpeg-turbo is developed in more open-source manner than original libjpeg.

Scope

libjpeg-turbo has same API/ABI as libjpeg so no package needs to be rebuilt

How To Test

You can use any program which uses libjpeg-turbo code. You should try to perform JPEG compression/decompression to and check if you don't see artefacts. You can also compare speed of the libjpeg-turbo against libjpeg, you should be able to visually check that libjpeg-turbo is really faster.

User Experience

A lot faster JPEG compression/decompression

Dependencies

462 packages (repoquery --alldeps --whatrequires libjpeg |wc -l) but no rebuild is needed due API/ABI compatibility

Contingency Plan

Revert to libjpeg when libjpeg-turbo hits some serious problems.

Documentation

http://sourceforge.net/projects/libjpeg-turbo

Release Notes

libjpeg library has been replaced by libjpeg-turbo library which has same API/ABI but is at least twice faster on all primary architectures and about 25% faster on secondary architectures

Comments and Discussion

See Talk:Features/libjpeg-turbo

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
+<!-- {{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
 {{admon/important | Set a Page Watch| Make sure you click ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
-{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
+{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }} -->
@@ Line 14: / Line 14: @@
 == Summary ==
-libjpeg-turbo is fork of the original libjpeg project. It contains numerous performance related enhancements and is at least twice faster in JPEG compression/decompression than original libjpeg on platforms with MMX/SSE instruction set. It has same API/ABI like original libjpeg and also runs on non-SSE platforms where is around 25% faster.
+[http://libjpeg-turbo.virtualgl.org/ libjpeg-turbo] is fork of the original [http://www.ijg.org/ libjpeg] project. It contains numerous performance related enhancements and is at least twice faster in JPEG compression/decompression than original libjpeg on platforms with MMX/SSE instruction set. It has same API/ABI like original libjpeg and also runs on non-SSE platforms where is around 25% faster.
 == Owner ==
@@ Line 20: / Line 20: @@
 == Current status ==
-* Targeted release: Fedora14
+* Targeted release: Fedora 14
-* Last updated: 2010-05-31
+* Last updated: 2010-07-02
-* Percentage of completion: 0%
+* Percentage of completion: 100%
 == Detailed Description ==
-<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+Everything is written in summary.
 == Benefit to Fedora ==
-<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
+Much faster JPEG compression/decompression library. JPEG codec is widely used and it is good to speed up core library which implements it. Additionally, libjpeg-turbo is developed in more open-source manner than original libjpeg.
 == Scope ==
-<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+libjpeg-turbo has same API/ABI as libjpeg so no package needs to be rebuilt
 == How To Test ==
-<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
+You can use any program which uses libjpeg-turbo code. You should try to perform JPEG compression/decompression to and check if you don't see artefacts. You can also compare speed of the libjpeg-turbo against libjpeg, you should be able to visually check that libjpeg-turbo is really faster.
-Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
-A good "how to test" should answer these four questions:
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this feature? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the feature is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
 == User Experience ==
-<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+A lot faster JPEG compression/decompression
 == Dependencies ==
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
+packages (repoquery --alldeps --whatrequires libjpeg |wc -l) but no rebuild is needed due API/ABI compatibility
 == Contingency Plan ==
-<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
+Revert to libjpeg when libjpeg-turbo hits some serious problems.
 == Documentation ==
-<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+* http://sourceforge.net/projects/libjpeg-turbo
-*
 == Release Notes ==
-<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
+libjpeg library has been replaced by libjpeg-turbo library which has same API/ABI but is at least twice faster on all primary architectures and about 25% faster on secondary architectures
-<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
-*
 == Comments and Discussion ==
-* See [[Talk:Features/YourFeatureName]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
+* See [[Talk:Features/libjpeg-turbo]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
-[[Category:FeaturePageIncomplete]]
+[[Category:FeatureAcceptedF14]]
 <!-- When your feature page is completed and ready for review -->
 <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Search

Features/libjpeg-turbo: Difference between revisions