Last modified: 2011-03-13 18:05:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T2269, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 269 - convert images to interlaced / progressive format
convert images to interlaced / progressive format
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
All All
: Lowest enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2004-09-01 22:53 UTC by Helge Hielscher
Modified: 2011-03-13 18:05 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Helge Hielscher 2004-09-01 22:53:12 UTC
Problem: it takes to long to load large images especially if one is using a
modem connection

Solution: convert all images automtically to the corresponding interlaced
(PNG/GIF) or progressive (JPEG) format, this can be done without data loss.

Comment 1 Tomer Chachamu 2005-02-21 17:56:22 UTC
Uses too much CPU resources.
Comment 2 Helge Hielscher 2005-02-21 18:45:14 UTC
a) the computer that does the conversion of the images does not have to be the
same computer that is serving the pages and/or images
b) this could be a process of very low priority (like nice -n 19) that works
from the eldest actively used images (=images that are not changed anymore) to
newer ones
c) many image converters are optimized for speed to the extend of beeing
programmed in assembly code
Comment 3 andrewpmk 2005-06-22 17:31:42 UTC
Against. Usually, interlaced images are larger because the Adam7 interlacing
mixes up the bytes, screwing up compression. I would rather load a smaller image
progressively than a larger image interlaced. Furthermore, the amount of CPU
time used by this is huge.
Comment 4 Rob Church 2005-08-30 18:23:22 UTC
Could this be made into a WikiProject, or whatever the Commons equivalent is?
Tag non-interlaced images and add them to a category, or would there be problems
from that, e.g. some weird copyright thing?
Comment 5 Rob Church 2005-12-17 02:21:48 UTC
No feedback on a possible user project to get this done, and we seem to be of
the opinion that it would consume too much of our precious resources as it is.
Agree with that; don't want to kill off the new NFS servers. ;-)
Comment 6 Zigger 2005-12-17 12:48:29 UTC
Changing resolution from WONTFIX to LATER, as there is a good track record of
decreasing CPU cost, increasing revenue and server numbers, and community
participation.  Some tests could be done on the impact of interlacing on sizes,
compressions, and CPU.
Comment 7 Nemo 2010-08-24 09:36:49 UTC
Revert to WONTFIX given bug 17645 comment 2 by Tim.

Note You need to log in before you can comment on or make changes to this bug.