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

Add file opening, in order to detect sequential access and checksum during i/o #1

Open
petersilva opened this issue Jun 1, 2018 · 0 comments
Labels
enhancement New feature or request speedup Important performance improvement wishlist not a priority, but a long term wish...

Comments

@petersilva
Copy link
Contributor

Currently, the library is trigerred on file close, not open. The idea being that we want the final version of a file, after all writes have occurred. However, if we only start working on the post when the file is closed, then in order to calculate the checksum, we have to read the entire file again. It would be better if we could:
set a offset in the file to 0, and initialize the checksum, then as long as the writes are sequential, update the checksums as the writes go by, so that when the file is closed, the checksum is already available.

Saving a file read on large files is a huge win. On the current HPC mirroring use case, the client refused to use checksumming because of the overhead of the extra read. With this mod, the overhead should drop to essentially 0 for many cases.

@petersilva petersilva added enhancement New feature or request speedup Important performance improvement labels Jun 1, 2018
@petersilva petersilva added the wishlist not a priority, but a long term wish... label May 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request speedup Important performance improvement wishlist not a priority, but a long term wish...
Projects
None yet
Development

No branches or pull requests

1 participant