mimalloc icon indicating copy to clipboard operation
mimalloc copied to clipboard

Performance impact of mi_collect

Open t0x1c opened this issue 4 years ago • 1 comments

Greetings, I have exact case described in mi_collect documentation: one long-running thread allocates enormous amount (from tens of thousands to hundreds of thousands per second) of small (1Kb-64Kb) blocks which are then processed/released by dozens of other worker threads.

What is the performance impact of calling mi_collect every 60 seconds? What is the difference between force and non-force modes and their relative performance? Is there a difference in performance that depends on thread calling mi_collect (thread that originally allocated memory vs unrelated housekeeping thread)?

t0x1c avatar Jun 15 '21 08:06 t0x1c

Also curious about these questions. Is the answer from the developers that we should just measure it ourselves?

davidgaleano avatar Jan 24 '24 12:01 davidgaleano