You can find all published reports here:

List of Published Reports (Internal)

Overview

This week's testing concentrated on identifying bottlenecks and potential improvements, specifically aimed at achieving higher blobs per block. Initial tests removed Lodestar and Nimbus to determine their impact on blob throughput. Subsequently, consensus-layer (CL) specific tests were conducted using Geth as the execution layer (EL), particularly assessing the performance impacts of enabling or disabling GetBlobsV2 across different CL clients.

• Achieves ~15% higher blob counts with GetBlobsV2 enabled
• More column processing failures with GetBlobsV2 enabled
• CLs which processed more data column sidecar verification had shorter overall verification time compared to those validated less
• Bandwidth doesn’t seem to be a huge bottleneck at the moment
• Some client specific issues found

Performance

1. Combination of ELs/CLs

Devnet-20 Dashboard

Devnet-20 Blobs/Block

Devnet-20 Block Time

A test was conducted with a mix of EL and CL pairs (Grandine, Lighthouse, Prysm, Teku combined with Geth, Nethermind, and Reth). Each client pairing included five nodes, totaling 60 nodes. The test achieved a maximum of approximately 40 blobs per block, notably lower than previous tests involving Lodestar and Nimbus. Despite lower peak performance, the overall network stability improved, including better block propagation times.

2. Lighthouse-Geth

Lighthouse-Geth w/ GetBlobs Dashboard

Blobs/Block on Lighthouse-Geth GetBlobsV2 On

Block Time on Lighthouse-Geth GetBlobsV2 On

Lighthouse-Geth w/o GetBlobs Dashboard

Blobs/Block on Lighthouse-Geth GetBlobsV2 Off

Block Time on Lighthouse-Geth GetBlobsV2 Off