Fixed #26 (Improve memory allocations; ditched io-streams) #27
Conversation
This file contains 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
|
Tests needs amending before I can safely merge this. |
|
This is not working well as I would have hoped. I will need to come back to this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR mainly fixes #26.
It also comes with the following breaking changes:
io-streamsin favour ofstreaming. The former, despite being a lovely library, wasn't the right fit for the job, because it uses a pre-allocated buffer which is not multiple of theblockSize, and this was creating lots ofreadandunRead, ultimately leading to huge memory spikes of 400+ MB on my machine, to decrypt a 1.22 GB file. The current implementation is constant at 2.4 MB of virtual memory.