Worker tuning has a ceiling: one machine. Past that, you split the suite across machines, which Playwright calls sharding.
lecture 11 of 170 completed
Sharding across machines
Beyond one machine's limit, you split the run. Balancing and report merging are where teams get it wrong.
What you'll learn
- How to split a run across machines
- Why blob reports must be merged
- Which runs are worth sharding and which are not
full course
Keep reading with the full course
The Foundations track and the first lessons in each framework are free. This lesson needs full course access. A course plan includes all lessons for Playwright, Cypress and Selenium.
See course plans →