Skip to content

Identify high-cost allocations #33

@GraphR00t

Description

@GraphR00t
  • A large number of small allocations incurs a large CPU cost due to GC scanning.
    (We should determine what are the most often allocated memory objects of small size)
  • Repeated large allocations trigger the GC more often

This issue should list Golang memory profiles from various Inox applications. Therefore it will remain open.

Identified allocations should be minimized.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions