Skip to content
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
Open

Benchmark storage related opcodes #112

Scooletz opened this issue Jul 18, 2023 · 0 comments
Labels
🐌 performance Perofrmance related issue

Comments

@Scooletz
Copy link
Contributor

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

  1. Zero vs. nonzero values - storing nonzero values is more costly than storing zero
  2. The current value of the slot vs. the value to store - changing the value of a slot is more costly than not changing it
  3. "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?
@Scooletz Scooletz added 🐌 benchmarks 🐌 performance Perofrmance related issue and removed 🐌 benchmarks labels Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐌 performance Perofrmance related issue
Projects
Paprika
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Scooletz