-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speed up performance massively with --maxWorkers=1 #1044
Comments
PR is welcome for README 😀 |
Wow, thank you for this, it is a massive improvement. I wonder what |
#1049 is one of the issues I think, I don't know which else causes perf issues. |
I ran into this issue as well. Would you consider adding a Known Issues section to the README and include this? I can submit a PR for this if needed, but Maybe we should wait until #1049 is merged to decide. |
#1049 is in master now. You can test it locally. Besides, setting isolateModules to true also speeds up a lot |
close as superseded by #1115 |
Issue :
This is not really an issue but rather a solution that could be mentioned in the docs.
I've been a bit annoyed with the performance of
ts-jest
. The VSCode jest plugin and watch mode were each taking 20-30s each run with the default config on a small-to-medium-sized project.This is with the default 2 workers:
Note: This is a computer with decent specs and 4 CPUs. I changed the command line to include
--maxWorkers=1
:which is a massive performance improvement.
The text was updated successfully, but these errors were encountered: