Lines Matching refs:an

34 call to an allocation function (malloc/free/etc). When a call
40 a call to an allocation function (malloc/free/etc) when `malloc_disable`
55 When set to zero, `mallopt(M_DECAY_TIME, 0)`, it is expected that an
60 When set to non-zero, `mallopt(M_DECAY_TIME, 1)`, an allocator can delay the
66 thread to handle the purge, so the decay is only handled when an
77 When called, `mallopt(M_PURGE, 0)`, an allocator should purge and release
86 These are the tests that should be run to verify an allocator is
205 not be used as absolutes for determining if an allocator is worth using.
226 frees are not counted. Forty allocations is an arbitrary number that could
243 As with the other microbenchmarks, an allocator with numbers in the same
362 When evaluating an allocator, one of the most important traces is the
373 is fragmenting badly will show an increase in RSS. The best trace for
374 tracking fragmentation is system\_server.txt which is an extremely long
376 up and down a bit, but stays mostly the same so an allocator that fragments
377 badly would likely show an abnormal increase in RSS on this trace.
403 every does an allocation at the same time as another thread.