Approximately halve memory usage #66
Merged
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
After the recent major refactor to fix a correctness bug in the type-checker, the inference engine continued to hang onto the execution result which it no longer needed. This is now no longer the case, resulting in an approximate halving of maximum memory usage. In addition, this also makes the maximum number of bytes that can be operated on in a single VM memory operation configurable externally, providing another point through which library clients can tune memory usage.
Closed
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.
Summary
After the recent major refactor to fix a correctness bug in the type-checker, the inference engine continued to hang onto the execution result which it no longer needed. This is now no longer the case, resulting in an approximate halving of maximum memory usage.
In addition, this also makes the maximum number of bytes that can be operated on in a single VM memory operation configurable externally, providing another point through which library clients can tune memory usage.
This mitigates #65, but does not totally fix the underlying inefficiencies of the current value representation.
Details
N/A
Checklist