Skip to content

[DecodeWithMemTracking] Research keeping track of all the nested double encoded structs #8675

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.

Sign up for GitHub

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

Jump to bottom
Open
serban300 opened this issue May 27, 2025 · 1 comment
Open

[DecodeWithMemTracking] Research keeping track of all the nested double encoded structs #8675

serban300 opened this issue May 27, 2025 · 1 comment
Assignees
@serban300

Comments

@serban300
Copy link
Contributor

We should investigate if we need this and how it can be implemented
@serban300 serban300 self-assigned this May 27, 2025
@bkchr
Copy link
Member

bkchr commented May 27, 2025

We should do this manually. This means we return the memory usage of DecodeWithMemTracking and then store it. When we do another decoding in the same context, we use the max_memory - whatever the other one returned.

@paritytech paritytech deleted a comment from alialobidm May 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@serban300 serban300

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bkchr @serban300