Skip to content

use custom allocator/memory pool for Token allocations #279

Open
@firewave

Description

@firewave

The new/delete calls for the Token allocations make up more than 30% of the Ir count when profiling with callgrind.

It might make sense to implement a custom allocator or memory pool to reduce that.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions