Page MenuHomePhabricator

convert images to interlaced / progressive format
Closed, DeclinedPublic

Description

Author: hhielscher

Description:
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.

Example:
non-interlaced:
http://de.wikipedia.org/upload/archive/0/07/20040818191627%21Leipzig1876.png
interlaced: http://de.wikipedia.org/wiki/Bild:Leipzig1876.png


Version: unspecified
Severity: enhancement

Details

Reference
bz269

Revisions and Commits

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 6:47 PM
bzimport set Reference to bz269.
bzimport added a subscriber: Unknown Object (MLST).

the.r3m0t wrote:

Uses too much CPU resources.

hhielscher wrote:

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

andrewpmk wrote:

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.

robchur wrote:

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?

robchur wrote:

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. ;-)

zigger wrote:

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.

Revert to WONTFIX given bug 17645 comment 2 by Tim.

epriestley changed the task status from Declined to Resolved by committing Unknown Object (Diffusion Commit).Mar 4 2015, 8:19 AM
epriestley added a commit: Unknown Object (Diffusion Commit).
Aklapper changed the task status from Resolved to Declined.Mar 4 2015, 11:29 AM
Aklapper claimed this task.