If your tests are I/O-bound, you can *probably* go wild with workers. But CPU-bound? Nah.
I’ve had success with `--workers=2 * cores` for API tests, but for E2E, I stick to cores - 1.
Playwright’s GitHub has some wild debates on this—worth a skim!
I’ve had success with `--workers=2 * cores` for API tests, but for E2E, I stick to cores - 1.
Playwright’s GitHub has some wild debates on this—worth a skim!
