Skip to content
This repository has been archived by the owner on Jun 26, 2023. It is now read-only.

optimize CheckIfPinned #6

Merged
merged 1 commit into from
Feb 18, 2021
Merged

Conversation

Stebalien
Copy link
Member

  1. Parallelize fetching from disk.
  2. Avoid re-visiting blocks we've already checked. Adding the same data over and over with small changes is pretty common.

This means ipfs block rm can actually complete (eventually), at least on my machine.

1. Parallelize fetching from disk.
2. Avoid re-visiting blocks we've already checked. Adding the same data
   over and over with small changes is pretty common.
Copy link

@gammazero gammazero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all looks good. The changes to ipldpinner are not actually necessary, since it is not used anymore (only there to support migration).

@Stebalien Stebalien merged commit d86645f into master Feb 18, 2021
@gammazero gammazero deleted the feat/optimize-check-if-pinned branch March 8, 2021 03:14
@aschmahmann aschmahmann mentioned this pull request Aug 23, 2021
62 tasks
Jorropo pushed a commit to ipfs/go-libipfs-rapide that referenced this pull request Mar 23, 2023
…k-if-pinned

optimize CheckIfPinned

This commit was moved from ipfs/go-ipfs-pinner@d86645f
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants