vitest: Degraded Test Execution Time
Describe the bug
Reopening: https://github.com/vitest-dev/vitest/issues/1844
The proposed solution, to set maxConcurrency
made the test run even slower.
See: https://github.com/Effect-TS/core/runs/7854754823?check_suite_focus=true
Reproduction
Same as before.
System Info
Same as before.
Used Package Manager
yarn
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 6
- Comments: 20 (12 by maintainers)
@mikearnaldi is it still an issue? I see that you halved the amount of tests that you had.
Side note: I was able to make your tests x2 times faster by disabling isolation in effect repo (since you don’t rely on any global state):
I was actually looking at the time spent in collections which seemed higher, yes overall it’s faster than before but far away from what it was in 0.14.2
Yeh that seems to have done down from 14mins -> 4mins after this commit: https://gitlab.com/bookmarkey/gui/-/merge_requests/75/diffs?commit_id=0eb1a6917cdd9b226937ecdda1571c29f3c4e3a7
Thanks @AriPerkkio
I managed to have decent performance by upgrading MSW and vite to their latest version, setup times are back to normal
Tested, doesn’t seem to make a big difference. Also Effect is zero dependency and with perfectly working ESM modules so not sure that flag even counts in my case