User blog comment:Rappy 4187/Technical Update: July 20, 2016/@comment-26154973-20160721213248/@comment-24473195-20160724122129

> The way I see it, if your platform isn't built for it why are you loading an obviously huge page?

Sometimes you don't have a choice, web pages are dynamic and may report a small page initially and load more on demand (e.g. when scrolling or showing ads). Accounting for every possibility is a fool's errand. For example, in the case of those massive galleries, wikia servers show webp in compatible browsers to reduce the size and improve performance.

>Huge pages are bad in general, sure, I agree.

I'm glad we agree on something.

>And I don't believe it's having your cake and eating it too when it was working fine before without noticeable performance problems.

Things always change, for better or worse. Naively,  mediawiki developers had initially built very few limits, and once they began experiencing serious server-side performance issues those limits were built in . It is also not just a matter of good pages for readers, editors may also experience severe issues editing those pages (see prior Phabricator link).

>The NewPP limit report for Ship Class suggests that the effect of the wikitext components of templates on page performance in minimal in this case.

It might be, http://kancolle.wikia.com/wiki/Ship_List_(Image) shows the problem will be solved by using a similar design without any wikia intervention.

>I see no problem when I try to load a 10000x10000 picture

That's a very strange perspective from someone who creates wiki pages. They are meant to be read or viewed, and if not, perhaps Google docs or another online collaboration platform might be better.

See also: https://en.wikipedia.org/wiki/Wikipedia:Avoid_template_creep