-
Notifications
You must be signed in to change notification settings - Fork 12
Closed
Description
We need to move away from using an in-memory data-store because there is no way to limit the amount of memory used. @wemeetagain mentioned that Lodestar uses an in-mem datastore that flushes to file-system. The code for that is https://github.com/ChainSafe/lodestar/blob/unstable/packages/beacon-node/src/network/peers/datastore.ts#L71
If lodestar has a datastore we can use, we should use that, otherwise we should migrate to use file-system directly and then update to use lodestar strategy.
from #18 (comment)
### Action items before close
- [x] ensure the helia-http-gateway version deployed on Tiros is the latest version
- [x] Use file-based datastore
- [ ] Use mem->file flushing datastore & blockstore
- [x] Investigate potentially hanging promises for helia-all & helia-delegated-routing? tiros jobs not finishing: https://github.com/plprobelab/probelab-infra/issues/87
Metadata
Metadata
Assignees
Labels
No labels
