nspcc-dev / nspcc-dev/neofs-node
Find optimal metadata chain parameters
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Derive from fsChainProtocol or set explicitly? It's important characteristic, and given the fact that you use short blocks, it's likely shouldn't be set to a default.
Either change it or create an issue for further meta chain parameters tuning, may require some load-testing.
Originally posted by @AnnaShaleva in https://github.com/nspcc-dev/neofs-node/pull/3991#discussion_r3342244095
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating fsChainProtocol and the metadata-chain parameter definitions. Determine whether the parameters should be derived or set explicitly, then use load-testing to compare choices and document a justified configuration or a follow-up tuning issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100