- Mentioned In
- T46310: Thumbnail cache should be automatically discarded after 6 months
T77453: RFC for blocking arbitrary thumbnail sizes over a certain size
T357: Organize a developer sprint on thumbnails changes
E187: RFC Meeting: triage meeting (2016-05-25, #wikimedia-office)
T134670: SelectFileWidget: Improve the thumbnail area (size, image appearance)
qgil wrote on 2014-08-14 14:11:05 (UTC)
Ok, understood. https://www.mediawiki.org/wiki/Requests_for_comment/Standardized_thumbnails_sizes has your name as author (which is certainly true, but incomplete, and might confuse more people apart from me).
@MarkTraceur, do you know who should on this RfC?
qgil wrote on 2014-08-20 16:24:04 (UTC)
I just want to know who is currently pushing for this RfC (if anybody): https://www.mediawiki.org/wiki/Requests_for_comment/Standardized_thumbnails_sizes
So don't assign it to me either? :-D
Re thinking thumbnails processing is in the hands of the Multimedia team. They conducted some changes already.
The RFC itself is merely to gather related informations at a central place since that topic been raised a few times before I wrote it.
Again, I don't think this should be blocked on Multimedia, since we don't have much to say about media storage/thumbnailing processes these days. If Performance or others have ideas, they should move forward with them without necessarily waiting on us.
On the other hand, this may be undesired or obviated per more recent discussions.
@fgiunchedi @Gilles If I recall correctly, this proposal mainly came from an operational concern regarding Swift storage use for thumbnails. Concern being that we're currently allowing any arbitrary thumbnail size to be generated, which are then indefinitely stored in Swift.
Removing support for arbitrary sizes from MediaWiki (or made inaccessible via Varnish or Swift-proxy), has impact and compatibility complexity that has thus-far stalled the task without a viable outcome.
I'm curious if this task is obsolete or whether it's worth reviving. Specifically, because we now use Thumbor for generating thumbnails. Speaking with @Gilles, I get the impression that we're planning to instead ensure we only store the subset of common sizes in Swift, but keep supporting requesting of other sizes, by letting them always pass through for on-demand generating from Thumbor. And given Varnish in front of it all, we still cache outliers that happen to be popular.
That's correct, mw prerenders certain thumbnail sizes and we've been cleaning up swift as part of a goal (https://wikitech.wikimedia.org/wiki/Swift/Thumbnails_Cleanup). With my swift hat on I believe the current situation is good enough, IOW the non-prerendered sizes were negligible in terms of requests and space. Some of the bigger sizes were prerendered but rarely requested, so we've stopped prerendering those altogether.