You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the blob compressor works on its payload block by block. This robs the underlying lzss compressor of some opportunities to find longer back references. When recompressing the entire blob payload on sample Sepolia blobs, we get the following results:
We already knew that wholesale compression would have yielded better results, though perhaps not to this extent. It was avoided to ensure the latency for the compression of a single block is low. In order to get both benefits, I propose that the Write method be kept as is, but to add methods StartOptimizer(period Duration) and StopOptimizer(). The optimizer runs in that background, performing wholesale compression periodically. Its results are voided if a new block has been submitted while recompression was running.
Note: This will not affect the decompressor.
Pitfalls: Async work is tricky and errors are hard to reproduce.
Problem Statement
Currently the blob compressor works on its payload block by block. This robs the underlying lzss compressor of some opportunities to find longer back references. When recompressing the entire blob payload on sample Sepolia blobs, we get the following results:
Proposed Solution
We already knew that wholesale compression would have yielded better results, though perhaps not to this extent. It was avoided to ensure the latency for the compression of a single block is low. In order to get both benefits, I propose that the
Write
method be kept as is, but to add methodsStartOptimizer(period Duration)
andStopOptimizer()
. The optimizer runs in that background, performing wholesale compression periodically. Its results are voided if a new block has been submitted while recompression was running.Note: This will not affect the decompressor.
Pitfalls: Async work is tricky and errors are hard to reproduce.
@gbotrel @jpnovais thoughts?
Reference
The text was updated successfully, but these errors were encountered: