https://bugzilla.wikimedia.org/show_bug.cgi?id=29111
--- Comment #38 from MZMcBride <[email protected]> 2011-07-24 22:53:55 UTC --- (In reply to comment #37) > Maybe the devs should disable cache once on e.g. mediawiki.org to see how slow > 1.17 really is? > > It's not super slow, but SLOWER. And that's the main reason for me not to > upgrade altho it would fix a few bugs for me. I prefer waiting for > ResourceLoader 2. This is a fair point, though largely outside this context. Caching is a band-aid that allows developers and system administrators to ignore the ridiculous amount of time that it takes to, e.g., render certain articles. If thousands of readers were required to wait 30 seconds in order to read their favorite articles, there would be much more progress toward making the parser less slow and horrible. As it is, most readers hit a cached layer of the rendered HTML, so viewing their favorite articles is quite quick. That said, your issue seems to not have a fixed source other than "1.17", and the parser has been slow for much longer than that. If you could provide something actionable here ("X is Y times slower on 1.17 than it was on 1.16, so please fix X"), there would be something to work with and resolve. As it is, you're simply claiming (largely based on anecdotal testing) that 1.17 is slower. It very well may be, but until you (or someone else) can diagnose the problem(s), this bug isn't going to go anywhere. I might go as far as to say that this bug should be resolved as "invalid" until there's something actionable, but that's a bit rude and that'll happen eventually (in a few months) assuming this bug stays on the same trajectory. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
