chore: bootstrap improvements.

[charlielye]

• l1-contracts cli cache bootstrappable.
• noir-contracts cli cache bootstrappable.
• bootstrap.sh will always attempt to pull from cli cache if the user has docker and aws-credentials.
• bootstrap.sh full will skip trying to use the cache.
• avm-transpiler builds on focal for better compatability.
• New script remove_old_images removes all docker images for a repo, older than the current content hash. Prevents local disk usage explosion. Called both after bootstrapping from cache, and as part of bootstrap_docker.sh.
• Reduced retry from 10s to 5s. Can be disabled with RETRY_DISABLED=1 env var.

[AztecBot]

Benchmark results

Metrics with a significant change:

• batch_insert_into_append_only_tree_16_depth_ms (2): 14.4 (+33%)
• batch_insert_into_append_only_tree_16_depth_hash_ms (2): 0.796 (+33%)

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 a2c0caed 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	54,212	214,436	855,332
l1_rollup_calldata_gas	259,868	1,019,864	4,060,316
l1_rollup_execution_gas	354,054	1,139,312	4,281,717
l2_block_processing_time_in_ms	1,264 (-1%)	4,769	18,990
note_successful_decrypting_time_in_ms	218	604	2,169
note_trial_decrypting_time_in_ms	29.9 (-9%)	40.1 (+3%)	181 (-3%)
l2_block_building_time_in_ms	21,339	84,605	343,158
l2_block_rollup_simulation_time_in_ms	16,008	63,440	258,850
l2_block_public_tx_process_time_in_ms	5,307	21,089	84,062 (-1%)

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	16,400 (+10%)	31,727 (+9%)
note_history_successful_decrypting_time_in_ms	1,519 (+9%)	2,763 (+2%)
note_history_trial_decrypting_time_in_ms	178 (+6%)	238 (+3%)
node_database_size_in_bytes	18,706,512	35,876,944
pxe_database_size_in_bytes	29,923	59,478

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	334	44,664	27,457
private-kernel-ordering	214	45,777	14,627
base-rollup	1,741	175,344	933
root-rollup	83.7	4,192	825
private-kernel-inner	444	73,099	27,457
public-kernel-app-logic	274	32,254	25,379
merge-rollup	7.80 (-1%)	2,712	933

Tree insertion stats

The duration to insert a fixed batch of leaves into each tree type.

Metric	1 leaves	2 leaves	8 leaves	16 leaves	32 leaves	128 leaves	64 leaves	512 leaves	1024 leaves	2048 leaves	8192 leaves
batch_insert_into_append_only_tree_16_depth_ms	10.4	⚠️ 14.4 (+33%)	13.1 (+1%)	17.7 (+3%)	23.2	64.7	N/A	N/A	N/A	N/A	N/A
batch_insert_into_append_only_tree_16_depth_hash_count	16.9	17.5	23.0	31.6	47.0	143	N/A	N/A	N/A	N/A	N/A
batch_insert_into_append_only_tree_16_depth_hash_ms	0.602	⚠️ 0.796 (+33%)	0.554 (+1%)	0.546 (+3%)	0.483	0.446	N/A	N/A	N/A	N/A	N/A
batch_insert_into_append_only_tree_32_depth_ms	N/A	N/A	N/A	N/A	N/A	76.1 (+1%)	48.4	242	469	914	3,596
batch_insert_into_append_only_tree_32_depth_hash_count	N/A	N/A	N/A	N/A	N/A	159	96.0	543	1,055	2,079	8,223
batch_insert_into_append_only_tree_32_depth_hash_ms	N/A	N/A	N/A	N/A	N/A	0.469 (+1%)	0.495	0.442	0.438	0.434	0.432
batch_insert_into_indexed_tree_20_depth_ms	N/A	N/A	N/A	N/A	N/A	105	57.7	358	699 (+1%)	1,381	5,488
batch_insert_into_indexed_tree_20_depth_hash_count	N/A	N/A	N/A	N/A	N/A	197	104	691	1,363	2,707	10,771
batch_insert_into_indexed_tree_20_depth_hash_ms	N/A	N/A	N/A	N/A	N/A	0.499	0.503	0.486 (+1%)	0.478	0.477	0.477
batch_insert_into_indexed_tree_40_depth_ms	N/A	N/A	N/A	N/A	65.1	N/A	N/A	N/A	N/A	N/A	N/A
batch_insert_into_indexed_tree_40_depth_hash_count	N/A	N/A	N/A	N/A	110	N/A	N/A	N/A	N/A	N/A	N/A
batch_insert_into_indexed_tree_40_depth_hash_ms	N/A	N/A	N/A	N/A	0.562	N/A	N/A	N/A	N/A	N/A	N/A

Miscellaneous

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

Metric	0 deployed contracts	1 deployed contracts
tx_size_in_bytes	15,388	36,001

Transaction processing duration by data writes.

Metric	0 new note hashes	1 new note hashes
tx_pxe_processing_time_ms	577	1,503

Metric	0 public data writes	1 public data writes
tx_sequencer_processing_time_ms	0.0305 (+2%)	654

[fcarreiro]

Thank you Charlie! I tried this PR by bootstrapping the whole thing from cache, then modifying the avm-transpiler and just compiling that, then running yarn-project tests. All worked.

Some general comments:

1. Could you also update the README file to reflect the changes?
2. Does it make sense for external devs to try to use cache? (they will not have AWS credentials). In theory it shouldn't hurt, but I wonder if we should make using cache default or just strongly encourage it internally. (it will also fail on non-linuxes etc)

[fcarreiro]

This seems to be only supported at top level. For subprojects you have to use NO_CACHE=1 to prevent use of cache. Would it make sense to have one or the other for all files?

[fcarreiro]

Optional: would it make sense to add an echo on failure along the lines of: "If you want to use the cache install docker and set up your AWS credentials"?

[fcarreiro]

Charlie will address comments on follow up PR.