Investigate moving away from Node's default IPC mechanism

[mjesun]

Currently, jest-worker uses internal Node's IPC mechanism; which in turn uses JSON serialization to transmit objects.

We should investigate if we could gain some speed + versatility if we switched to use v8.serialize / v8.deserialize V8's APIs, which are exposed through the v8 module. These methods allow to serialize Date and RegExp objects, and they also make possible to serialize circular references.

In addition to that, we should use some sort of transmission mechanism to pass native buffers between processes; xpipe seems to be a good solution for that.

[mjesun]

Assigning it to @BYK who is interested in experimenting with this.

Some code pointers:

• Internal send happens.
• Internal receive happens.
• Bootstrapping file we open in child processes.

[SimenB]

This has been investigated and abandoned, right?

[SimenB]

Yup, #5613. Feel free to reopen if you still wanna track it

[mjesun]

I'm not sure we ever investigated this. @rafeca, would you be interested in taking it?

Edit: yes, we did investigate for the v8.serialize part, and it was slower than JSON.

[github-actions]

This issue 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.