You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:
"Priority" labels will show how urgent this is for the team.
"Status" labels will show if this is ready to be worked on, blocked, or in progress.
"Need" labels will indicate if additional input or analysis is required.
GC is query all block cids from from datastore and then compare to pinned cids and remove the missing one by one. This is expensive and slow as if we have million cids on datastore.
Tracking for multiple GC related issues and enhancement proposals.
Currently Open Issues:
Historical Info; Closed Issues.
rm -rf
+ resync is faster #7213 IPFS Repo GC Is Unrealistic At Non-Trivial Scaleipfs repo gc
very slow #6322ipfs repo gc
very slowComments about current GC implementation: #1420
Enhancement effort: #4149
Block cache issues that may be pulled into GC work if block cache is also used for GC:
The text was updated successfully, but these errors were encountered: