Skip to content

Possible updates with the use of non-Rabin algorithms #19

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

Closed
DonaldTsang opened this issue Feb 26, 2018 · 5 comments
Closed

Possible updates with the use of non-Rabin algorithms #19

DonaldTsang opened this issue Feb 26, 2018 · 5 comments

Comments

@DonaldTsang
Copy link

According to some papers, FastCDC and Asymmetric Extremum has better performance.
It might be a good idea to have algorithms that can achieve better speeds while being secure.
FastCDC: https://www.usenix.org/system/files/conference/atc16/atc16-paper-xia.pdf
AE reference: http://www.ijarcsms.com/docs/paper/volume4/issue6/V4I6-0021.pdf

@fd0
Copy link
Member

fd0 commented Feb 26, 2018

Thanks a lot for the pointers! Please be aware that, at least for restic, we don't depend on the CDC algorithm being "secure" (whatever that means for a CDC algorithm) :)

@DonaldTsang
Copy link
Author

@fd0 I do have a hint that this project is related to IPFS, so from their perspective it has to be secure.
I do think though that in the experiment stage, security is not a concern at all.

@fd0
Copy link
Member

fd0 commented Feb 26, 2018

They are using a fork of this package, correct, but as far as I know they are also using it to just cut files into pieces and properly encrypt the pieces afterwards.

@DonaldTsang
Copy link
Author

DonaldTsang commented Feb 26, 2018

@fd0 And from what I see, they are currently stuck at a stage where the performance is not optimal.
That is why I am purposing something that can help the situation, hoping IPFS can improve.
ipfs-inactive/archives#134 ipfs-inactive/archives#136 ipfs-inactive/archives#137 ipfs-inactive/archives#142

@fd0
Copy link
Member

fd0 commented Feb 26, 2018

I appreciate the pointers to more recent algorithms for CDC! I also think this repo/package is the wrong place. It is meant to be used by restic, our backup program, and we won't change the chunking algorithm lightly, because that will cause problems for our users. For a backup program, the repository/storage format is the most important thing.

Besides, in our application of Rabin fingerprints, we don't see any performance problems, the algorithm and this implementation performs great for us :)

The nice people from IPFS have forked the package to a new repo, here: https://github.com/whyrusleeping/chunker

I'm therefore closing this issue for now, please feel free to add further comments. Thanks!

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