How does parallel testing in Pest 2 runs up to 80% faster?

[cristiancalara]

I've read the "This impressive result was only possible thanks to a complete rebuild of the parallel test core system. The new core incorporates advances techniques for process reuse between test case runs." note on the documentation, but not sure if there are a few specific areas in the code that someone could point me to. Or more technical information on how this was achieved?

We are trying to decide as a team if we should move a rather large test suite to Pest. Most of the members on the team are not sold on the syntax and the extra features. But they consider the speed improvements as worth moving to Pest. Now the question that arose is:

Could this improvement be added to the Paratest library directly and it will land there shortly? (as 80% seems like a huge performance boost). Or are there other caveats to this that made the Paratest maintainers not go with this approach (maybe riskier / maybe the performance improvements could be made only by making assumptions about the project using Laravel, etc)?

Any insight into this would be appreciated :)