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

Identify high-cost allocations #33

Open

GraphR00t opened this issue Jan 9, 2024 · 0 comments

Labels

builtins performance language performance

Contributor

GraphR00t commented Jan 9, 2024 •

edited

Loading

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.

GraphR00t added language performance builtins performance labels

GraphR00t changed the title ~~Determine what are the most often allocated memory objects of small size~~ Determine high-cost allocations

GraphR00t changed the title ~~Determine high-cost allocations~~ Identify high-cost allocations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment