Lines Matching refs:allocation

6 [SQL Allocation Trace Benchmark](#sql-allocation-trace-benchmark),
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`
67 allocation operation occurs. For server processes, this can mean that
69 and no other allocation calls are made. The `M_PURGE` option is used to
92 of allocation routines such as what happens when a non-power of two alignment
100 The allocation tests are not meant to be complete, so it is expected
130 allocator on Android. One is allocation speed in various different scenarios,
174 These are the benchmarks to verify the allocation speed of a loop doing a
175 single allocation, touching every page in the allocation to make it resident
176 and then freeing the allocation.
188 The last value in the output is the size of the allocation in bytes. It is
241 allocation in bytes.
246 since they simulate real world allocation profiles.
253 in a real world allocation scenario. SQL operations were chosen as a
295 address space consumed, speed of allocation. They are designed to
321 in all threads since it collapses all of the allocation operations to occur
346 Every 100000 allocation operations, a dump of the RSS and VA space will be
353 the allocation calls (malloc/memalign/posix_memalign/realloc/free/etc).
365 rather than delete them. When that happens, it can lead to allocation
403 every does an allocation at the same time as another thread.