Reduce loading time

[mitschabaude]

PR to reduce the startup time of SnarkyJS
Closes #1065

Bindings: o1-labs/o1js-bindings#116
Mina: MinaProtocol/mina#13925
Snarky: o1-labs/snarky#829

Benchmark (node):

./run src/examples/benchmarks/import.ts

Time to import at various steps:

• e09772d: 1763ms - initial
• MinaProtocol/mina@8ee87dc: 1183ms - remove expensive poseidon param conversion
• MinaProtocol/mina@d232a0d: 1061ms - compute vk hash lazily
• MinaProtocol/mina@78de73e: 950ms - compute dummy tx lazily
• MinaProtocol/mina@7d9fa28: 877ms - compute Pickles dummy data lazily
• o1-labs/o1js-bindings@7e2696b: delay getting number of workers; only affects web (reduction by >100ms)
• afee400: 749ms - precompute and bundle hash prefix states instead of computing them at the top level
• latest: 585ms - avoid a bunch of other top level computation / avoid going through zarith when converting fields

Web flame graph of the first ~2 seconds, before:

Same flame graph after:

Note: There's basically no way to reduce this further within the current architecture. After this PR, most of the loading time of ~0.5sec comes from compiling the JS bundle, which is large. Of the time spent executing that bundle, most happens in core JSOO / OCaml libs. There's only about 50ms of top-level computation caused by Mina code. Some of which is just instantiating modules that we need. There's almost nothing left that we can get rid of.

[mitschabaude]

Note for reviewers: all the non-trivial changes are in the linked PRs (Mina, bindings, snarky)

[mitschabaude]

so, here's how this is supposed to work:

the new bindings.ts file imported here is written in TS, and contains code integrated with our normal codebase. It is exposed to JSOO by populating a global variable with an object. It gets imported as the first thing here so that the global variable is ready by the time JSOO code gets executed.

It may not be the cleanest thing to have an implicit dependency like that, but it's a huge improvement over the status quo, where all JS code used in JSOO has to be part of an ugly file containing outdated syntax which can use neither TS nor normal imports.

[L-as]

Can't you do the parsing lazily? You could use a dynamic import instead. If you use the separate jsoo compilation, you can maybe even import each separately lazily.

[mitschabaude]

Can't you do the parsing lazily? You could use a dynamic import instead. If you use the separate jsoo compilation, you can maybe even import each separately lazily.

we can (we do) but then you can't use the lib directly after import. we'd get back await isReady