chore: Optimise bb.js package size and sandox/cli dockerfiles to unbloat final containers.

[charlielye]

We're making efforts to streamline our container sizes. They shouldn't really be any "bigger" than an equivalent npm download and package install.

• bb.js inlined the two wasms creating a 50mb monster index.js because:
  • The wasm symbol stripping was not being done after wasm creation in the bb wasm container.
  • The two wasms ended up duplicated in the bundle due to webpack inline the workers, and seemingly unable to reason they're the same thing even using chunks.
• Given that bb.js now has a synchronous singleton instantiation of the wasm, we can plumb that compiled module into the async worker version to avoid the duplication.
• The above fixes reduce the size of index.js to 11mb, and this compresses very nicely to ~1.7mb for serving over web.
• We still produce a "runnable" container in bb.js, for executing the tests, but we use yarn pack to produce the publishable artefact, which is what we import downstream. This cuts out 300mb of node_modules, which may just get reimported downstream, but should at least remove duplication and strip back to production on dependencies.
• We remove gubbins from bb wasm container that circuits cpp needed, as we have killed it off.
• For sandbox and cli we:
  • Fix the "productionify" step to clear the cache after to the prod install. It was originally this way around due to use of pnp instead of node_modules (if we really care about size, maybe we should reconsider pnpifying the final runtime?). But, if we're not using pnp, we should purge the .yarn/cache.
  • Blow away all the src folders as they're non negligible in size.
  • Building final "slim" image cherry picks a little more carefully to avoid pulling in some unneeding things (e.g. nargo).

Estimate of compressed containers at present:
cli size from 277MB to ~98MB
sandbox from 311MB to ~107MB

If we can get a shared layer between these two containers we effective half the data again. Maybe in a later PR.
A pure npm install, once compressed was about 87MB so this would be almost on par.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@types/lodash.compact	3.0.7	None	+0	3.8 kB	types
@types/lodash.clonedeepwith	4.5.7	None	+0	3.88 kB	types
@types/sha256	0.2.0	None	+0	2.92 kB	types
vite	4.4.8	eval, network, filesystem, shell, environment	+0	3.33 MB	vitebot
lodash.partition	4.6.0	None	+0	68.1 kB	jdalton
@esm-bundle/chai	4.3.4	None	+0	1.04 MB	joeldenning
@docusaurus/plugin-ideal-image	2.4.1	environment	+0	22.5 kB	slorber
@nomicfoundation/hardhat-chai-matchers	2.0.2	None	+0	254 kB	fvictorio
@libp2p/peer-id	3.0.2	None	+1	78.7 kB	npm-service-account-libp2p

[AztecBot]

Benchmark results

Metrics with a significant change:

• note_history_trial_decrypting_time_in_ms (10): 233 (-35%)
• note_trial_decrypting_time_in_ms (32): 57.7 (+88%)

Detailed results

All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.

This benchmark source data is available in JSON format on S3 here.

Values are compared against data from master at commit d356bac7 and shown if the difference exceeds 1%.

L2 block published to L1

Each column represents the number of txs on an L2 block published to L1.

Metric	8 txs	32 txs	128 txs
l1_rollup_calldata_size_in_bytes	45,444	179,588	716,132
l1_rollup_calldata_gas	222,972	868,064	3,449,456
l1_rollup_execution_gas	842,059	3,595,172	22,204,825
l2_block_processing_time_in_ms	2,026	7,722	31,532
note_successful_decrypting_time_in_ms	324 (+2%)	930 (+3%)	3,337
note_trial_decrypting_time_in_ms	33.4 (+21%)	⚠️ 57.7 (+88%)	200 (+1%)
l2_block_building_time_in_ms	18,884	74,242 (-2%)	297,941 (+1%)
l2_block_rollup_simulation_time_in_ms	15,324	60,232 (-3%)	241,795 (+1%)
l2_block_public_tx_process_time_in_ms	3,510	13,858	55,582

L2 chain processing

Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric	5 blocks	10 blocks
node_history_sync_time_in_ms	22,885	44,637
note_history_successful_decrypting_time_in_ms	2,263	4,360 (-1%)
note_history_trial_decrypting_time_in_ms	166 (+3%)	⚠️ 233 (-35%)
node_database_size_in_bytes	3,305,783	3,649,592
pxe_database_size_in_bytes	29,748	59,307

Circuits stats

Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit	circuit_simulation_time_in_ms	circuit_input_size_in_bytes	circuit_output_size_in_bytes
private-kernel-init	201 (+1%)	43,077	20,441
private-kernel-ordering	115	25,833	9,689
base-rollup	2,546	659,500	873
root-rollup	88.5 (-5%)	4,072	1,097
private-kernel-inner	261	64,484	20,441
public-kernel-private-input	172	25,203	20,441
public-kernel-non-first-iteration	169	25,245	20,441
merge-rollup	11.1	2,592	873

Miscellaneous

Transaction sizes based on how many contracts are deployed in the tx.

Metric	0 deployed contracts	1 deployed contracts
tx_size_in_bytes	10,323	25,938

[ludamad]

LGTM