[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

ArielGlenn closed this task as "Resolved". ArielGlenn claimed this task. ArielGlenn added a comment. There's no point in having this open for a once a year check in, so I'll go ahead and close it. When capacity planning needs to be done for dbs in the regular course of things, this can be

[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

LSobanski removed a project: SRE. LSobanski added a comment. Thanks for all the responses. Based on the above I think that a regular (yearly?) check-in should still happen but there are no immediate actions for #SRE . TASK DETAIL

[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

Ladsgroup added a comment. Commons is now the biggest section and by far. It used to be so much worse that wikidata dwarfed in comparison. The thing is: It has almost exclusively nothing to do with the SDoC. The biggest tables were templatelinks, categorylinks, externallinks, etc. It has

[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

Marostegui added a comment. I think even if they grow a lot, with the new set of servers, we still have 6.6TB free (76% free disk space)...I'd be surprised if we grow that much in 3 years. TASK DETAIL https://phabricator.wikimedia.org/T226093 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

ArielGlenn added a comment. In T226093#8512308 , @LSobanski wrote: > The task's original intent was to cover planning "over the next 3 years" starting in 2019. @ArielGlenn is the task still relevant, can it be closed, do we need a new

[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

LSobanski added a comment. The task's original intent was to cover planning "over the next 3 years" starting in 2019. @ArielGlenn is the task still relevant, can it be closed, do we need a new one? TASK DETAIL https://phabricator.wikimedia.org/T226093 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

Ladsgroup added a comment. If we can clean up the image table (T275268: Avoid capacity issues from the image table holding the text of pdf/djvu files as part of their metadata ) it'll give us leeway for the structured data I assume. TASK DETAIL

[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

Restricted Application added a project: wdwb-tech-focus. TASK DETAIL https://phabricator.wikimedia.org/T226093 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Nintendofan885 Cc: Nintendofan885, Ladsgroup, Abit, matthiasmullie, Marostegui, Addshore,

[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

Marostegui added a comment. Following my IRC chat with @ArielGlenn - `revision` and `slots` table on s4 (commonswiki) are still under reasonable sizes. We just decrease the size of the `revision` table as we applied the MCR schema changes there. As of now, the sizes on disk are: -

[Wikidata-bugs] [Maniphest] T226093: Capacity planning for Commons Structured Data

ArielGlenn added a comment. Updated (ouch!) F32352585: commons_slots.png TASK DETAIL https://phabricator.wikimedia.org/T226093 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: ArielGlenn Cc: