Use write buffer when writing resulting image #21
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This modification resulted in large performance gain on my system (5x faster).
|
No performance benefit for me, but works. |
|
test with Intel G5400 change from ~950Kb/s to ~10Mb/s. Also cpu is always at 100% so with faster cpu gain can be better. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This modification resulted in large performance gain on my system (5x faster). Reasoning behind this change is that we should not call the kernel with each sector (512b) and instead accumulate more data before sending it.
Please review the change carefully, this is my first encounter with golang and I do not understand it very well (but I used this code to successfully recover my 2T WD drive)