https://bugzilla.wikimedia.org/show_bug.cgi?id=37295
--- Comment #2 from Krinkle <[email protected]> 2012-06-05 08:55:12 UTC --- So it won't reduce the size of the to-be-parsed amount of scripts. As the loader framework requires these configuration variables. I briefly discussed this with Max during the Berlin Hackathon 2012. His primary concern wasn't the data itself but the cache fragmentation. Right now we've got it set up like this I believe (example for mediawiki.org): * Startup - Hardcoded in the HTML (the only script link hardcoded in HTML) - Version parameter: None (shouldn't be since it is hardcoded in the page cache) - Cache age: 5 minutes - URL: https://bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&* * Core modules - Only if isCompatible() returned true - Loaded from ResourceLoaderStartupModule - Contains the core library of jQuery and mediaWiki - Version parameter: Yes - Cache age: ∞ (30 days in practice) - URL: //bits.wikimedia.org/www.mediawiki.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20120528T141202Z By moving mw.config to the second request we reduce the amount of data put into the "every 5 minutes" loop. However that does introduce a problem that has to be solved, which I believe was the reason mw.config was put into startup in the first place: Version parameter. Configuration comes from many places. We need a highly reliable timestamp for this. Assuming for the minute that we can come up with such a reliable source of timestamps and max() them. Is it worth it? Is it worth it to invalidate the core-modules request every time the configuration changes? This would mean that every time LocalSettings.php (or in the case of WMF, most files in wmf-config) changes the cache for jquery and mediawiki will be invalidated. The alternative would be to put them in a separate group, but that doesn't work. In order to use groups in the loader one needs to have the actual loader, and it can't load itself. So we'd have to add a separate document.write just for mw.config? -- 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
