Lines Matching full:these

29 These are functions that are used to implement a memory leak detector
51 These are mallopt options that Android requires for a native allocator
86 These are the tests that should be run to verify an allocator is
90 The bionic unit tests contain a small number of allocator tests. These
139 These are the microbenchmarks that are part of the bionic benchmarks suite of
140 benchmarks. These benchmarks can be built using this command:
144 These benchmarks are only used to verify the speed of the allocator and
147 For all of these benchmark runs, it can be useful to add these two options:
174 These are the benchmarks to verify the allocation speed of a loop doing a
178 To run the benchmarks with `mallopt(M_DECAY_TIME, 0)`, use these commands:
183 To run the benchmarks with `mallopt(M_DECAY_TIME, 1)`, use these commands:
189 useful to look at these kinds of benchmarks to make sure that there are
190 no outliers, but these numbers should not be used to make a final decision.
191 If these numbers are slightly worse than the current allocator, the
196 These are the benchmarks that examine how the allocator handles multiple
199 The first set of these benchmarks does a set number of 8192 byte allocations
204 results, but, as mentioned before, these microbenchmark numbers should
210 To run the benchmarks with `mallopt(M_DECAY_TIME, 0)`, use these commands:
215 To run the benchmarks with `mallopt(M_DECAY_TIME, 1)`, use these commands:
220 For these benchmarks, the last parameter is the total number of allocations to
230 To run the benchmarks with `mallopt(M_DECAY_TIME, 0)`, use these commands:
235 To run the benchmarks with `mallopt(M_DECAY_TIME, 1)`, use these command:
240 For these benchmarks, the last parameter in the output is the size of the
245 a switch. The trace benchmarks are more important than these benchmarks
254 benchmark because these operations tend to do lots of malloc/realloc/free
257 To run the benchmarks with `mallopt(M_DECAY_TIME, 0)`, use these commands:
262 To run the benchmarks with `mallopt(M_DECAY_TIME, 1)`, use these commands:
267 These numbers should be as performant as the current allocator.
273 To run the benchmark, use these commands:
286 To run the benchmark, use these commands:
291 These calls are used to free unused memory pages back to the kernel.
294 These benchmarks measure all three axes of a native allocator, RSS, virtual
308 And these two benchmark executables:
314 These benchmarks display RSS, virtual memory consumed (VA space), and do a
326 To generate these traces, see the [Malloc Debug documentation](https://android.googlesource.com/pla…
329 To run these benchmarks, first copy the trace files to the target using
330 these commands:
357 The performance numbers for these runs tend to have a wide variability so
405 Run these benchmarks thusly:
411 traces and display data. It takes many minutes to complete these runs in