go/oasis-node/config: Make consensus `BlockCacheSize` parametric (BadgerDB)

Open
#6,344 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
blockchain, databases

Research direction

Start by reviewing the existing runtime block-cache parameterization and the discussion linked from the issue, then locate the consensus NodeDB BadgerDB configuration. Done means BlockCacheSize can be configured parametrically for consensus in the same way as the runtime; no specific test file is named.

Written by the indexing model from the issue text.

Description

I think it would be a good idea to make block cache size of consensus NodeDB parametric, like is currently the case for the runtime.

See existing discussion https://github.com/oasisprotocol/oasis-core/pull/6339#discussion_r2390566200.

Dominant language
Go
Stars
369
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oasisprotocol/oasis-core

All issues in oasisprotocol/oasis-core

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.