https://bugzilla.wikimedia.org/show_bug.cgi?id=34104
Sam Reed (reedy) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Sam Reed (reedy) <[email protected]> 2012-02-08 14:40:42 UTC --- Revision rows: enwiki - 460014306 dewiki - 87901921 commons - 42765689 So, dewiki is the next biggest wiki, with enwiki being over 5 times larger (in respect of the number of revision rows) I do believe the sha1 is basically populated and such throughout the code, but it's only real use is in the xml dumps We would need to comment out explicit reads/writes on the field, but shouldn't be too painful code wise. Would this mean the smaller wikis should be doable somewhat easily? ie dewiki should be under 10 hours (giving some margin for guestimation) Enwiki is obviously will be one of the latter wikis to be upgraded to 1.19 archive rows: enwiki - 35621907 dewiki - 13702308 commons - 5344901 I'm presuming doing archives ar_sha1 is going to be quite a bit quicker? revision is nearly 13 times larger than archive is on enwiki Could we get away with just doing a delayed release of this. So the first XML dumps after 1.19 don't have any revision sha1 hashes? Oh well. Obviously they're not greedily populated, so it's not going to be much of an issue. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
