Lines Matching refs:it

55 When set to zero, `mallopt(M_DECAY_TIME, 0)`, it is expected that an
62 implementation, but it should be a reasonable amount of time. The jemalloc
73 made by default. The idea is that it allows application frees to run a
79 possible, this call should clear thread cached memory if it exists. The
100 The allocation tests are not meant to be complete, so it is expected
147 For all of these benchmark runs, it can be useful to add these two options:
175 single allocation, touching every page in the allocation to make it resident
201 Only the time it takes to do the allocations is recorded, the frees are not
225 benchmark, only the time it takes to do the allocations is tracked, the
283 mallinfo benchmark, it's not necessary for this to be better than the previous
319 on a thread as if it was rerunning the real trace. The only issue is that
321 in all threads since it collapses all of the allocation operations to occur
324 so it is not possible to create a completely accurate replay.
348 For the most part, the intermediate data can be ignored, but it is always
352 The performance number is a measure of the time it takes to perform all of
355 it takes to make the pointer completely resident in memory is included.
365 rather than delete them. When that happens, it can lead to allocation
379 NOTE: When a native allocator calls mmap, it is expected that the allocator
384 If the native allocator creates a different name, then it necessary to