SolsDB: Solve the Ethereum’s bottleneck caused by storage engine

Ethereum’s block synchronization process interacts with the storage engine in two parts: waiting for state data to be read while processing transactions and waiting to write data after processing is complete. Presently, Ethereum utilizes the LSM-tree-based storage engine that not only falls short of meeting Ethereum’s read performance requirements but also presents additional mismatches. In this paper, we propose the single-level ordered log structure database (SolsDB), which fully utilizes state data features to satisfy the workload requirements of Ethereum block synchronization process and suggest novel interactions to deliver state data features to the storage engine. The write feature of state data is utilized to store state data in blocks and the file is globally ordered, which avoids write amplification caused by compaction. By delivering the read feature, the Parser module is crafted to parse the query key, enabling direct file location without the need for level-by-level querying, thus addressing the issue of read amplification. Extensive experiments are conducted to validate the performance of SolsDB. Compared with LevelDB, SolsDB improves read performance by up to 4.7x, reduces read tail latency by 68.7% to 83.3%, and reduces the write amplification factor by 49.1% to 76.1%.