Type of activity: Pre-scheduled session. Unconference would also be OK.
Main topic: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/How_to_manage_our_technical_debt / https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Handling_wiki_content_beyond_plaintext
The way MediaWiki stores information in a relational database is not very efficient. In some respects we are reaching the limits of the current design. We need to explore options to address this issue, like normalization, denormalization, partitioning, as well as alternative storage technologies.
Concrete problems include the size of the revision table and the performance impact of redundant storage of page titles in link tables.
- A roadmap proposal for improving storage scalability
Current status of the discussion
No centralized discussion, but the issue as been brought up in the context of various discussions, see below.
- T107595: [RFC] Multi-Content Revisions
- T142980: RFC: Create a content meta-data table
- T105652: RfC: Content model storage
- T589: RFC: image and oldimage tables
- T100705: Consider using Cassandra/restbase in place of external store
- T6715: Allow comments longer than 255 bytes