Skip to content

Conversation

@arepala-uml
Copy link
Contributor

  1. Added badgerCacheSize to the config (dingo.yaml) to allow control over Badger's memory usage.
  2. Ensured backward compatibility by providing a default badgerCacheSize fallback when the config is not set.
  3. Added WithBadgerCacheSize and it sets the maximum cache size (in bytes).
  4. Updated node.go and database initialization to pass the configured cache size.
  5. Passed badger cache size through node.go to database and blob store layers.
  6. Updated all unit test cases where database.New() was invoked.

Closes #694

…via badgerCacheSize

Signed-off-by: Akhil Repala <arepala@blinklabs.io>
…er cache size

Signed-off-by: Akhil Repala <arepala@blinklabs.io>
@arepala-uml arepala-uml marked this pull request as ready for review June 14, 2025 16:38
@arepala-uml arepala-uml requested a review from a team as a code owner June 14, 2025 16:38
@arepala-uml arepala-uml requested review from agaffney and wolf31o2 June 14, 2025 16:38
…and update default cache size to 1GB

Signed-off-by: Akhil Repala <arepala@blinklabs.io>
@arepala-uml arepala-uml requested a review from wolf31o2 June 16, 2025 03:47
@wolf31o2 wolf31o2 merged commit 9a2114c into main Jun 16, 2025
11 checks passed
@wolf31o2 wolf31o2 deleted the badger_cache_size branch June 16, 2025 19:05
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.

Make Badger cache size configurable

3 participants