hyperweb-io / hyperweb-io/starship
improvement: better resource usage for chains
- Dominant language
- TypeScript
- Stars
- 77
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
## Overview
To be able to run longer running devnets, we need to use less storage (main factor contributing to resource overflow).
## Currently
The chains are run with default configuration, saving everything to storage of the Pods, this storage is limited by the disk space per node available.
## Proposal
For longger running chains, we need the capability to use less resources, maybe pruning every so many blocks to keep the storage in check.
Need to look into the configs for each chain to use less storage.
## Wacky idea
Maybe we perform pruning action per chain node based on the available storage. Not sure how this can be done if at all.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the per-chain default configuration and the Pod storage settings, then compare how each chain supports pruning or reduced storage. Done requires a defined, tested configuration strategy that keeps long-running devnets within node storage limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100