New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Benchmark storage related opcodes #112

Open

Scooletz opened this issue Jul 18, 2023 · 0 comments

Labels

🐌 performance

Contributor

Scooletz commented Jul 18, 2023

The cost of an SSTORE dependends on the existing value and the value to be stored:

Zero vs. nonzero values - storing nonzero values is more costly than storing zero
The current value of the slot vs. the value to store - changing the value of a slot is more costly than not changing it
"Dirty" vs. "clean" slot - changing a slot that has not yet been changed within the current execution context is more costly than changing a slot that has already been changed

Consider this as each SSTORE will always require loading the value first to estimate the gas price. Should there be a bloom filter or something?

The text was updated successfully, but these errors were encountered:

Scooletz added this to Paprika

Scooletz converted this from a draft issue

Scooletz added 🐌 benchmarks 🐌 performance and removed 🐌 benchmarks labels

Scooletz moved this from Todo to Low Priority / Not Needed ATM in Paprika

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment