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

filestore-db size #28

Open
jefft0 opened this issue Feb 11, 2017 · 4 comments
Open

filestore-db size #28

jefft0 opened this issue Feb 11, 2017 · 4 comments

Comments

@jefft0
Copy link

jefft0 commented Feb 11, 2017

Using the latest master branch of ipfs-filestore.

$ ipfs version --all
go-ipfs version: 0.4.5-dev-8566ce2
Repo version: 4
System version: amd64/linux
Golang version: go1.7.3

On a "modest" set of webcam video files totalling 245 GB, I use ipfs filestore add to add each one. Initially, the total size of ~/.ipfs/filestore-db is a reasonable 200MB. Each day I add a few more files until the files total 460GB (less than double). But now ~/.ipfs/filestore-db has grown to 1400 MB (seven times the original size). And it seems to keep disproportionately growing.

Do I need to run a utility to compact the .ldb files?

@kevina
Copy link

kevina commented Feb 20, 2017

Thank you so much for your feedback. Unfortunately it does not look like my code is going to go in as is. Instead something much much simpler is going to go in initially. Please see ipfs#3629.

The state of my fork is unclear, so for now please leave this open.

@kevina
Copy link

kevina commented Feb 21, 2017

Note edit, I meant to say "much much simpler" in case you didn't figure it out already.

@jefft0
Copy link
Author

jefft0 commented Feb 21, 2017

Is the branch in ipfs#3629 at a point where I can test it?

@kevina
Copy link

kevina commented Feb 27, 2017

Sorry, for the delay in getting back to you. I unfortunately don't think it is and at this point a lot of it is beyond my control. I am going to try to try to write up something to let everyone know what is going on; however, how my pull request was handled is a personal sore spot for me, and it is very difficult for me to write something without it sounding aggressive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants