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

Apply RocksDB documentation suggestions to reduce memory usage #3963

Closed

Conversation

ahamlat
Copy link
Contributor

@ahamlat ahamlat commented Jun 13, 2022

Apply some RocksDB documentation suggestions to reduce memory usage.

  • Set format_version to 5
  • set optimize_filters_for_memory to true
  • Increase block size to 32K
  • set cache_index_and_filter_blocks to true (this may have a big impact on performances)

Signed-off-by: Ameziane H. [email protected]

PR description

Fixed Issue(s)

Documentation

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

Changelog

@ahamlat ahamlat force-pushed the reducte-rocksdb-memory-usage branch from 6ae66a1 to 1f8384d Compare June 13, 2022 12:37
@ahamlat ahamlat changed the title [DOT NOT MERGE] Apply RocksDB documentation suggestions to reduce memory usage Apply RocksDB documentation suggestions to reduce memory usage Jun 15, 2022
@jclapis
Copy link
Contributor

jclapis commented Jun 17, 2022

image

Resyncing mainnet on a Rock 5B (but set the JVM heap size to 2G to emulate a Raspberry Pi), so far it's well within the limits. I'll let it run for a few days to make sure it stays around this level.

@ahamlat ahamlat closed this Jun 17, 2022
@ahamlat
Copy link
Contributor Author

ahamlat commented Jun 17, 2022

will create another PR.

@vanjan
Copy link

vanjan commented Jun 29, 2022

what's the other PR?

@ahamlat
Copy link
Contributor Author

ahamlat commented Jul 6, 2022

@vanjan : #3985

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 this pull request may close these issues.

3 participants