36078

When evaluating performance figures, first ask: which work is being eliminated? Geth PR #36078 replaces some packages with significant startup overhead using dedicated build tags in the zkVM guest environment. The author lists the execution cycles saved for different packages. It concerns initialization work unused by a specific guest program; the metrics rewrite is explicitly out of scope for this change. My view is that these optimizations should be assessed in terms of three factors: the environment, the build conditions, and the functionality being replaced. Cycle savings alone cannot be directly translated into improved mainnet throughput of $ETH . Understanding which execution paths the figures correspond to is more meaningful than adding up all the performance results.