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

Oficial rules? #5

Open
dpc opened this issue Jul 24, 2017 · 1 comment
Open

Oficial rules? #5

dpc opened this issue Jul 24, 2017 · 1 comment

Comments

@dpc
Copy link
Contributor

dpc commented Jul 24, 2017

So I have been using this benchmark to optimize rdedup, and I was doing some test and improvements, etc. At some point, I'd like to add rdedup to the official "results". And I am wondering what are the actual rules? Eg. 1MB chunks are big, and rdedup results are much better with smaller chunks. I am guessing other tools might also benefit from different settings too.

As every benchmark encourages competition, it is only fair if the rules are clear.

For starter:

  • can we tune settings for every program?
  • do have to stick to the same settings in "linux" (small files) vs "vm" (big image)?
@gilbertchen
Copy link
Owner

There aren't such rules and I don't think there should be. All you need to do is to state your settings clearly to the degree that other people can reproduce your results easily. In my option this benchmark serves two purposes: to give users a rough idea of how fast each tool is, and to help developers identify if there is any room for improvement.

As for the size of chunks, chunks smaller than 1MB would incur too much overhead when uploading to cloud storages.

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