You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cache multisite installations like single site installations #377
Given a WP install restores a cached installation, but Given a WP multisite install runs wp core install-network on top of it in every scenario. That makes a multisite setup about five times slower than a single site one (around 0.46 seconds versus 0.1 seconds locally).
The step runs about 140 times per suite run across 9 bundled commands. Caching the network installation the same way as the single site installation would make both setups equally cheap.
Measured in #382 against the test suites of 8 bundled commands, with three runs with and without the change each (see the pull request description for the numbers).
Caching the network installation saves about 0.4 seconds per multisite scenario, which is below the run-to-run variation of the suites. The total Behat time changed by +1.1%, and only cache-command showed a difference outside that variation (−5.9%). The change did not cause any failures.
Closing, as the gain does not justify the additional caching logic.
Activity
schlessera commentedon Oct 31, 2026
Measured in #382 against the test suites of 8 bundled commands, with three runs with and without the change each (see the pull request description for the numbers).
Caching the network installation saves about 0.4 seconds per multisite scenario, which is below the run-to-run variation of the suites. The total Behat time changed by +1.1%, and only cache-command showed a difference outside that variation (−5.9%). The change did not cause any failures.
Closing, as the gain does not justify the additional caching logic.