Lines Matching refs:benchmark

6 [SQL Allocation Trace Benchmark](#sql-allocation-trace-benchmark),
21 When evaluating a native allocator, make sure that you benchmark both
147 For all of these benchmark runs, it can be useful to add these two options:
152 This will run the benchmark XX times and then give a mean, median, and stddev
159 Which will lock the benchmark to only run on core XX. This also avoids
162 benchmark moves from big to little or vice-versa, this can cause scores
207 This benchmark is designed to verify that there is no performance issue
223 The other variation of this benchmark is to always do forty allocations in
225 benchmark, only the time it takes to do the allocations is tracked, the
249 This benchmark is a trace of the allocations performed when running
252 This benchmark is designed to verify that the allocator will be performant
254 benchmark because these operations tend to do lots of malloc/realloc/free
270 This benchmark only verifies that mallinfo is still close to the performance
273 To run the benchmark, use these commands:
282 This benchmark tracks the cost of calling `mallopt(M_PURGE, 0)`. As with the
283 mallinfo benchmark, it's not necessary for this to be better than the previous
286 To run the benchmark, use these commands:
299 To build this benchmark:
308 And these two benchmark executables:
337 Run the benchmark thusly:
371 There is no specific benchmark for memory fragmentation, instead, the RSS
400 This is a benchmark that treats the trace data as if all allocations
410 When run without any arguments, the benchmark will run over all of the