vm: include vm context in the embedded snapshot

[joyeecheung]

The first commit comes from #44258

vm: make ContextifyContext template context-independent

Instead of creating an object template for every ContextifyContext,
we now create one object template that can be reused by all
contexts. The native pointer can be obtained through an embdder
pointer field in the creation context of the receiver in the
interceptors, because the interceptors are only meant to be invoked
on the global object of the contextified contexts. This makes
the ContextifyContext template context-independent and therefore
snapshotable.

vm: include vm context in the embedded snapshot

Include a minimally initialized contextify context in the embedded
snapshot. This paves the way for user-land vm context snapshots.

vm: avoid unnecessary property getter interceptor calls

Access to the global object from within a vm context is intercepted
so it's slow, therefore we should try to avoid unnecessary access
to it during the initialization of vm contexts.

• Remove the Atomics.wake deletion as V8 now does not install it
  anymore.
• Move the Intl.v8BreakIterator deletion into the snapshot.
• Do not query the Object prototype if --disable-proto is not set.

This should speed up the creation of vm contexts by about ~12%.

Refs: #44014
Refs: #37476

[nodejs-github-bot]

Review requested:

• @nodejs/startup

[mscdex]

s/embeded/embedded in commit message

[joyeecheung]

Rebased on top of #44258 and added a commit that makes use of the snapshot to speed up the initialization of the vm contexts a bit.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/46050/

[joyeecheung]

From the CI: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1174

20:50:54 confidence improvement accuracy (*) (**) (***) 20:50:55 vm/create-context.js n=1000 *** 7.34 % ±2.99% ±3.97% ±5.17% 20:50:55 vm/run-in-context.js withSigintListener=0 breakOnSigint=0 n=1000 -6.14 % ±6.57% ±8.75% ±11.40% 20:50:55 vm/run-in-context.js withSigintListener=0 breakOnSigint=1 n=1000 1.28 % ±12.90% ±17.18% ±22.38% 20:50:55 vm/run-in-context.js withSigintListener=1 breakOnSigint=0 n=1000 -6.66 % ±8.39% ±11.16% ±14.53% 20:50:55 vm/run-in-context.js withSigintListener=1 breakOnSigint=1 n=1000 -1.86 % ±11.60% ±15.44% ±20.10% 20:50:55 vm/run-in-this-context.js withSigintListener=0 breakOnSigint=0 n=1000 -0.87 % ±7.80% ±10.38% ±13.52% 20:50:55 vm/run-in-this-context.js withSigintListener=0 breakOnSigint=1 n=1000 3.06 % ±22.00% ±29.27% ±38.10% 20:50:55 vm/run-in-this-context.js withSigintListener=1 breakOnSigint=0 n=1000 -1.53 % ±9.74% ±12.96% ±16.87% 20:50:55 vm/run-in-this-context.js withSigintListener=1 breakOnSigint=1 n=1000 -0.26 % ±12.00% ±15.97% ±20.79% 

It seems that I needed to bump up the number of iterations (--set n=1000) to get a stable number from the benchmarks though.

[goloveychuk]

I've found that (inside build snapshot)

constvm=require('vm')constcontext=vm.createContext();console.log(context,vm.isContext(context))constglobal2=vm.runInContext('this',context,)

throws an error

TypeError: The "contextifiedObject" argument must be an vm.Context. Received an instance of Object 

should it be fixed in this PR or next?

[joyeecheung]

@goloveychuk My plan is to implement user-land vm context it in another PR (because that requires more refactoring to the lifetime management of the bindings), this only adds support for vm context in the embedded snapshot, which isn't that complex.

[joyeecheung]

Opened #44277 and transferred the discussions there, in case this PR goes too off-topic. @goloveychuk please use that thread for discussions about user-land modules instead, thanks

[juanarbol]

This is not landing cleanly in v16.x