graphprotocol / graphprotocol/graph-node
The chain blocks table is extremely large, how do I make it smaller?
Open
Nobody has claimed this yet.
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
I'm running a graph node on base with some deployed subgraphs. The blocks table in chain1 has now grown to over 2.5 TB. How can I shrink it? I've already performed a prune to 10 million blocks with graphman, but the blocks table is still extremely large. How do I free up memory?
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
The report names graphman pruning and the chain1 blocks table but no files or tests; start by tracing graphman’s prune entry point and the storage path for that table. Reproduce the post-prune size or inspect the reported behavior, then document a verified way to reduce the table or explain why pruning does not affect it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100