Skip to content
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

fix(workers): use advanced serialization by default in child process workers #10983

Merged
merged 3 commits into from
Apr 20, 2022

Conversation

SimenB
Copy link
Member

@SimenB SimenB commented Dec 28, 2020

Summary

This introduces parity in serialization implementation between the child process and worker thread implementations.

Extracted from #10981.

Test plan

Unit test tweaked, so green CI

@MichaReiser
Copy link
Contributor

Thanks.

Can you see any performance differences when running the benchmark script?

Should we 'keep' the default serialization for jest-hastemap? Would you mind doing a short verification if the performance did not degrade?

@SimenB SimenB force-pushed the advanced-serialization branch from 495d114 to d384694 Compare December 28, 2020 17:23
@SimenB SimenB added this to the Jest 28 milestone Feb 24, 2022
@SimenB SimenB force-pushed the advanced-serialization branch 2 times, most recently from d0594fe to 1afe39f Compare February 24, 2022 18:48
@SimenB SimenB force-pushed the advanced-serialization branch from 250a95d to cd22c47 Compare April 20, 2022 11:33
@SimenB SimenB merged commit 5e570b9 into jestjs:main Apr 20, 2022
@SimenB SimenB deleted the advanced-serialization branch April 20, 2022 12:20
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants