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.

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

Avoid caching in benchmarks for storage opcodes #1441

Closed
xgreenx opened this issue Oct 23, 2023 · 0 comments · Fixed by #1469
Closed

Avoid caching in benchmarks for storage opcodes #1441

xgreenx opened this issue Oct 23, 2023 · 0 comments · Fixed by #1469
Assignees

Comments

@xgreenx
Copy link
Collaborator

xgreenx commented Oct 23, 2023

No description provided.

@xgreenx xgreenx self-assigned this Oct 23, 2023
@xgreenx xgreenx changed the title Try to use random key/values in benchmarks for storage opcodes Avoid caching in benchmarks for storage opcodes Oct 23, 2023
xgreenx added a commit that referenced this issue Nov 2, 2023
Closes #1441

- Disabled cache for blocks in the table
- Removed usage of in memory transaction in benchmarks and replaced it
with checkpoint
- Added bloom filter
- Added customization of the block cache
crypto523 pushed a commit to crypto523/fuel-core that referenced this issue Oct 7, 2024
Closes FuelLabs/fuel-core#1441

- Disabled cache for blocks in the table
- Removed usage of in memory transaction in benchmarks and replaced it
with checkpoint
- Added bloom filter
- Added customization of the block cache
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant