scripts/test: Use maxWorkers=4 when running on CI #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It seems that Jest runs much faster in Travis when it's ran with this flag. E.g. for one particular project, this made the frontend testing time drop from 20 minutes to 2 minutes.
|
I know this is merged, but would https://facebook.github.io/jest/docs/en/cli.html#maxworkers-num |
You mean that so it would have used the number of CPUs instead of hard coded 4? Might have been good too, but the number of CPUs is irrelevant here, since the constraining resource here is amount of memory rather than amount of CPUs. Therefore some hard coded small value might be better. (E.g. if they make e.g. 64 CPUs available for the job runner container in Travis, but it still has very small memory.) |
|
That is indeed true 🙂 Just wanted to check 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems that Jest runs much faster in Travis when it's ran with this
flag. E.g. for one particular project, this made the frontend testing
time drop from 20 minutes to 2 minutes.