AWS Researcher: go-verkle has four major performance bottlenecks and has submitted multiple optimization proposals.

ME News Report, April 2nd (UTC+8), Amazon’s cloud computing division AWS core protocol researcher Ekleen Kaur and Everton Fraga conducted high-pressure testing on the Ethereum Verkle tree underlying implementation go-verkle at EthCC[9], revealing four major performance bottlenecks hindering statelessness deployment. 1. During tree updates, a large number of shadow nodes that do not logically exist but occupy physical space are generated, leading to approximately 35% redundant inflation of state data; 2. The database index key design contains many duplicate path information, increasing storage overhead by about 50%; 3. Converting the in-memory tree structure into proofs involves a large number of memory copies rather than pointer references, resulting in deserialization speeds 24 times slower than the optimized theoretical value, which may cause proof verification timeouts under high load; 4. Verkle tree implementations in clients written in different languages such as Go, Rust, Nimbus, etc., generate proofs for specific edge cases that are not mutually recognizable, posing a risk of unexpected forks after upgrades. The two researchers stated that AWS has submitted multiple optimization proposals to the Ethereum core repository, focusing on restructuring deserialization logic to eliminate memory copies. Once completed, node operation efficiency is expected to improve more than threefold, laying the foundation for the formal integration of Verkle trees. (Source: Foresight News)