answer question on ethresear.ch: Clarify whether Geth’s default 2 GB DB cache is sufficient #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qizhou
approved these changes
Jan 27, 2026
qizhou
left a comment
qizhou
left a comment
There was a problem hiding this comment.
LGTM. Please paste the results also in ethresearch
dajuguan
approved these changes
Jan 27, 2026
doc/paper.md
Outdated
|
|
||
| Would you say that geth’s default db cache configuration (i.e. 2GB) is sufficient for the time being? | ||
|
|
||
| ### Answer |
There was a problem hiding this comment.
LGTM. Maybe make the answer a #### subsection to make the Q&A structure clearer?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an answer to the question raised in the ethresear.ch thread about whether Geth’s default 2 GB DB cache is sufficient.
In practice, yes — especially under Geth’s default path‑based state scheme: path‑based key locality significantly improves cache efficiency compared to the hash‑based model used in the article.
Benchmarks show ~0.34 disk I/Os per Get with a 2 GB cache on path‑based storage vs ~1–2 I/Os under hash‑based storage, meaning the default cache size is adequate for today’s workloads.