refactor: keep track of blocks emitting/cancelling messages#4028
Conversation
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. Values are compared against data from master at commit L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 16 txs.
Circuits statsStats on running time and I/O sizes collected for every circuit run across all benchmarks.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contracts are deployed in the tx.
Transaction processing duration by data writes.
|
PhilWindle
left a comment
There was a problem hiding this comment.
Just a couple of minor nits.
| } | ||
|
|
||
| getL1BlockNumber(): Promise<bigint> { | ||
| getL1BlockNumber() { |
There was a problem hiding this comment.
Could you comment this please?
This PR refactors the archiver store to use `@aztec/kv-store` instead of lmdb directly. It is stacked on top of #4028. The diff looks massive but all it does is split the archiver store into individual pieces to better separate them conceptually (blocks, logs, contracts, messages) and replace direct uses of lmdb with the data structures from kv-store.
…tocol#4028) This PR refactors the archiver to keep track of which L1 block last emitted messages or cancelled messages (similar to how it discovers L2 blocks) in order to make the synch process more efficient.
This PR refactors the archiver store to use `@aztec/kv-store` instead of lmdb directly. It is stacked on top of AztecProtocol#4028. The diff looks massive but all it does is split the archiver store into individual pieces to better separate them conceptually (blocks, logs, contracts, messages) and replace direct uses of lmdb with the data structures from kv-store.
This PR refactors the archiver to keep track of which L1 block last emitted messages or cancelled messages (similar to how it discovers L2 blocks) in order to make the synch process more efficient.