Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipfs pin ls gets slower as the pinned objects increase #3874

Open
kikoncuo opened this issue Apr 23, 2017 · 2 comments
Open

ipfs pin ls gets slower as the pinned objects increase #3874

kikoncuo opened this issue Apr 23, 2017 · 2 comments
Labels
kind/bug A bug in existing code (including security flaws) topic/perf Performance

Comments

@kikoncuo
Copy link

kikoncuo commented Apr 23, 2017

Version information:

go-ipfs version: 0.4.8-
Repo version: 5
System version: amd64/windows
Golang version: go1.8

Type: bug

Severity: medium

Description:

ipfs pin ls is really fast when the repo size is small, but the bigger it gets the slower it is, this affects other operations, such as calling the gc after unpinning an object. My cpu usage during this process is not very high (ipfs.exe is using around 4-5% CPU).
Is this behaviour normal or it should use more resources to finish faster?

I understand, that listing a lot of files may take a long time, this is usually not a problem since listing all the pinned files without specifying a file or at least a type is not usually done, my main worry is when deleting a file from the repo and using the repo gc command since deleting just one big file can take a long time (6.6min to delete a 20gb video), that may be too long for a regular user.

@whyrusleeping
Copy link
Member

whyrusleeping commented Apr 24, 2017

@kikoncuo This is a good thing to bring up. Its a known problem, though youre the first to open an issue about it, This puts it clearly on our TODO list.

It definitely should be faster, so lets try and make it so.

@Kubuxu Kubuxu added kind/bug A bug in existing code (including security flaws) topic/perf Performance labels Apr 24, 2017
@prcolaco
Copy link

prcolaco commented Nov 1, 2018

Any news about this bug? It continues to be really slow on 0.4.17 and is keeping some scripts of my nodes from executing properly... Would be really great to have this solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) topic/perf Performance
Projects
No open projects
Development

No branches or pull requests

4 participants