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

Update RocksDB default block cache size #4132

Merged

Conversation

ahamlat
Copy link
Contributor

@ahamlat ahamlat commented Jul 19, 2022

Update RocksDB default block cache size to mitigate a performance regression from #3985.

Signed-off-by: Ameziane H ameziane.hamlat@consensys.net

PR description

We can see in the dashboard below that we have some blocks behind with the RocksDB block cache default value 8 MB, and Besu with block cache size 128 MB is performing better (no blocks behind).

image

Fixed Issue(s)

#4128

Documentation

  • I thought about documentation and added the doc-change-required label to this PR if
    updates are required.

Changelog

Signed-off-by: Ameziane H <ameziane.hamlat@consensys.net>
Signed-off-by: Ameziane H <ameziane.hamlat@consensys.net>
Copy link
Contributor

@matkt matkt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, waiting for a second approval

@matkt
Copy link
Contributor

matkt commented Jul 19, 2022

the tests are failing because of this modification @ahamlat . it seems to need a quick update

Signed-off-by: Ameziane H <ameziane.hamlat@consensys.net>
@ahamlat
Copy link
Contributor Author

ahamlat commented Jul 19, 2022

The unit tests are fixed.

@garyschulte garyschulte merged commit 915854c into hyperledger:main Jul 19, 2022
eum602 pushed a commit to lacchain/besu that referenced this pull request Nov 3, 2023
* Update RocksDB default block cache size.

Signed-off-by: Ameziane H <ameziane.hamlat@consensys.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants