Reduce embedded IPFS node resource usage - #2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Profiling a metadata-indexer instance showed that ~95% of memory (~2GB RSS) and CPU
was consumed by the embedded IPFS node acting as a full network participant:
announcing every cached block to the DHT and serving blocks to other peers.
Changes
fsrepo.Initis a no-op when the repoalready exists, so config changes in code never reached deployed nodes. The config
is now persisted on every start via
repo.SetConfig(identity is preserved).Provide.Enabled=false,Bitswap.ServerEnabled=false) — the node is a pure consumer.Routing.Type=delegated) — provider lookups gothrough HTTP routers instead of running a DHT client.
StorageMax=2GB+ a periodic GC goroutine(
corerepo.PeriodicGC); theenable-gcExtraOpt is daemon-only and had no effect.and discarding an RSA key on every launch).
reconnectgoroutine that logged the full peer list every 3 minutes.Tests
Added tests covering repo creation (idempotency, identity preservation) and config
persistence/override on existing repos — no node startup or network required.