Forgot the memory usage cost for serialiseData #4486
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
kwxm
commented
Mar 22, 2022
| @@ -513,7 +513,7 @@ | |||
| "memory": { | |||
| "arguments": { | |||
| "intercept": 0, | |||
There was a problem hiding this comment.
I was tempted to add in a few words for extra overhead here but thought better of it.
bezirg
approved these changes
Mar 22, 2022
9 tasks
|
(I failed to update the cost-model-generation code here, but that's fixed in #4570.) |
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.
A massive PR for the memory cost of
serialiseData, which I forgot to do in #4480. We have to account for the size of the serialized object as a function of the size of the input, so I've gone for a factor of 2 to account for any overhead. A factor of 1 would probably be safe anyway though.