Performance/Runbook/Measure backend performance: Revision history

28 October 2022

• curprev 23:0523:05, 28 October 2022‎ imported>Krinkle‎ 60 bytes −10,934‎ Krinkle moved page Performance/Runbook/Measure backend performance to Performance/Guides/Measure backend performance

9 August 2022

• curprev 17:4817:48, 9 August 2022‎ imported>Ori‎ 10,994 bytes +721‎ More on benchmarking and load testing in production; remove reference to vtune (doesn't work on ARM, untested by us, alternatives exist, let's not recommend something we haven't tried)

17 June 2022

• curprev 21:0721:07, 17 June 2022‎ imported>Krinkle‎ 10,273 bytes +123‎ →‎See also: +mw:Manual:Profiling

13 June 2022

• curprev 16:5616:56, 13 June 2022‎ imported>Krinkle‎ 10,150 bytes +1,977‎ →‎Benchmarking: Copy from mw:PHP optimisation tips#Benchmarking, as written by @Tim Starling on 2 September 2021‎.

1 June 2022

• curprev 17:0217:02, 1 June 2022‎ imported>Krinkle‎ 8,173 bytes +8,173‎ Created page with "This provides an entrypoint for '''measuring performance of existing code'''. If you are starting a new project or otherwise have not yet set performance objectives, '''first read''' our guidance on Backend performance. == Production impact == Once code is in production, either during an incident or in the hours/days after deploying a new feature to a large wiki, the following are good starting points for measuring..."