Page MenuHomePhabricator

Encountered HTTP 429s while trying to load thumbnails of an image with many revisions
Open, Needs TriagePublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

What happens?: Some thumbnails are not displayed and browser log shows HTTP 429s

What should have happened instead?: The client JS should somehow queue up the images so they're only loaded on scroll.

Software version (skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.): I don't understand why if we can view up to 500 thumbnails at a time if the software cannot serve 500 images to a single client at the same time.

Event Timeline

Umherirrender subscribed.

When the thumbs are already generated and exists on the server it is possible to view all thumbs at once.
It is only the inital attempt to get the thumbs, because the server generates thumbs on request of the real image, not when the html is embedded.
The number of fresh thumbs is limited to avoid overload of the server, in that case the 429 is shown.

It appears for me now that all thumbs are generated and shown.

So it is possible to generate html with that count of images and it can work to show all thumbs to the user.

But I see nothing to fix here, because checking if a thumb exists or not and having another page for that case could be expensiver as a reload by the user.

Are thumbnails not created and cached upon image upload?

Are thumbnails not created and cached upon image upload?

No, no pre-generation of thumbs on wmf wikis, some wmf doc at https://wikitech.wikimedia.org/wiki/Media_storage#Thumbnail_handling
Inside MediaWiki it is called "transformVia404", see https://www.mediawiki.org/wiki/Manual:Thumb.php or https://www.mediawiki.org/wiki/Manual:$wgGenerateThumbnailOnParse

This is likely the same as T311004: HTTP 429 returned when rendering thumbnails for grayscale TIFF files

Actually.. no it's just a cache stampede I guess..