-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat/36/add benchmarks #70
feat/36/add benchmarks #70
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
benchmark setup looks great! got a question though, what do we do with it and when do we run it, should it be on the pipeline? what's the process?
Good question. I am not sure. @serg-temchenko what is usually the process? |
Considering that our proposal didn't contain a lot of information about this, I was thinking that the purpose is to run benchmarks with several types of files, such as small, medium, and large files. We should run each case multiple times, gather performance output, and include it in the documentation/README file of the crate. Is it possible to do with this setup? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks solid! let's generate those benchmarks and add them to the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I try to run the benchmarks using cargo bench
all tests are ignored. Tried a bunch of flags and nothing.
Please document how to run the benchmarks in the crate's README (and take the opportunity to make the specs list, an actual list, I f'd up when I wrote it 😅).
Do also run the benchmarks and document your findings in your PC — maybe @th7nder could also run them on his 24-core machine? 👀
The spec list for the storage provider? Uff :D |
I'd wait, but the tests are ignored, what gives?
I meant this: -CARv1 specification: https://ipld.io/specs/transport/car/carv1/
-CARv2 specification: https://ipld.io/specs/transport/car/carv2/
-UnixFS specification: https://github.com/ipfs/specs/blob/e4e5754ad4a4bfbb2ebe63f4c27631f573703de0/UNIXFS.md
+* CARv1 specification: https://ipld.io/specs/transport/car/carv1/
+* CARv2 specification: https://ipld.io/specs/transport/car/carv2/
+* UnixFS specification: https://github.com/ipfs/specs/blob/e4e5754ad4a4bfbb2ebe63f4c27631f573703de0/UNIXFS.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. From looking at the benchmarks I'm fairly sure that the filestore has a bug — i.e. doesn't de-duplicate blocks
Description
Added benchmarks for
mater
create.Important points for reviewers
Used: https://docs.rs/criterion/latest/criterion/
Checklist