Description
Release Engineering and ServiceOps plan to move some portion of production MediaWiki to use Kubernetes. The current option we've discussed is Test2Wiki as:
- In discussion with QTE, that wouldn't interfere with manual testing
- It would give the Kubernetes cluster real production traffic
This move may have unknown performance implications. And there are multiple performance aspects to consider. Filing this task to facilitate discussion about how best to handle performance testing during this transition process.
Preview environment
Performance can try the Kubernetes environment currently using the WikimediaDebug extension.
Which code to review
The environment and runtime are changing, which involves puppet changes and packaging/deployment changes.
Performance assessment
Please initiate the performance assessment by answering the below:
- What work has been done to ensure the best possible performance of the feature?
- Shellbox to ensure performant (and functioning) file uploads
- Work in MediaWiki/config to load yaml to ensure speedy deployment of configuration changes
- What are likely to be the weak areas (e.g. bottlenecks) of the code in terms of performance?
- Unknown
- Are there potential optimisations that haven't been performed yet?
- Unknown
- Please list which performance measurements are in place for the feature and/or what you've measured ad-hoc so far. If you are unsure what to measure, ask the Performance Team for advice: performance-team@wikimedia.org.