The benchmark itself has some issues; namely, the unit tests are run on a single thread but the end to end tests are merely parallelized one per thread. I would

The benchmark itself has some issues; namely, the unit tests are run on a single thread but the end to end tests are merely parallelized one per thread. I would guarantee he's not getting 100% CPU utilization on the M1 machine if those tests are anything like the ones I see. BDD/E2E tests have a lot of waiting for buttons to load on pages, clicking/moving the cursor, and waiting for backend results. A proper test would simply run _all_ the BDD tests in parallel to properly max out the CPU and let the OS handle the thread switching.