Skip to content
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.

MaxMemory dangerous #21

Open
ddv2005 opened this issue Jul 18, 2022 · 0 comments
Open

MaxMemory dangerous #21

ddv2005 opened this issue Jul 18, 2022 · 0 comments

Comments

@ddv2005
Copy link

ddv2005 commented Jul 18, 2022 •
edited
Loading

Could you explain a reason to implement MaxMemory using a simple json/encoding to count the byte size? Because simple json/encoding using at least TWICE memory than actual objects!!! MaxMemory should keep memory usage in boundaries but instead it guarantee than memory boundaries would be breached. MaxMemory not just useless - it is dangerous in current implementation because actual memory usage 3 times more.
@ddv2005 ddv2005 changed the title MaxMemory useless because using a simple json/encoding to count the byte size MaxMemory dangerous Jul 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ddv2005