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

MaxMemory dangerous #21

@ddv2005

Description

@ddv2005

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions