Skip to content
New issue

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

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

Already on GitHub? # to your account

Efficient sparse file handling #14

Open
andreygursky opened this issue Jan 30, 2016 · 6 comments
Open

Efficient sparse file handling #14

andreygursky opened this issue Jan 30, 2016 · 6 comments

Comments

@andreygursky
Copy link

Daniel,
what's about support of variable block length? Perhaps this could be used to mark (very) large holes in files, thus making them to be patched/transferred at once.

P.S. By the way, do you plan to continue working on go-sync or maybe you are about to switch it into an unmaintained project? Or a third alternative: no active development anymore, only if there are patches from others. Maybe you could update https://github.com/Redundancy/go-sync#current-state with additional infos about how you see the further development process of go-sync. You could also clarify, what are TODOs, that you're personally about to finish, and what are nice things to implement additionally, but rather a long term ones and/or welcome to do by others.

@Redundancy
Copy link
Owner

go-sync uses a fixed block size like rsync, but will combine continuous missing ranges when it analyses the file. It can then decide the maximum range length that it will do in a single blocksource request.

You can decrease the block size and get more accurate diffs, but this will be at the cost of an increased index size and significantly more comparisons that are needed.

@jsilhan
Copy link

jsilhan commented Mar 16, 2016

By the way, do you plan to continue working on go-sync or maybe you are about to switch it into an unmaintained project?

I also wonder what would the future be of this project. @Redundancy, do you know who is already using go-sync in production?

@bwmarrin
Copy link

Same here :)

@Redundancy
Copy link
Owner

I don't know of anyone who is using gosync in production, and still wouldn't recommend it personally.

I'd like to continue to poke at it, but it hasn't been easy to find the free time and energy recently with work commitments, so I also don't want to promise anything. I was hoping that some people might start contributing, because I don't think it's something that I could really support solo anyway. At the very least I'd like to separate the commandline tool from the underlying library with something like gb.

Apologies if that's disappointing anyone :)

@bwmarrin
Copy link

It is a bit sad :) I'd love and would be willing to help, but my knowledge of rsync inner workings is pretty non existent. But having a cross platform rsync compatible alternative that runs natively on Windows would be a godsend and I always hoped someday this package would lead the way.

@Redundancy
Copy link
Owner

Noted - I'll try and pick up the effort again once things are a little less crazy.

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

No branches or pull requests

4 participants