Lines Matching refs:as

92 of allocation routines such as what happens when a non-power of two alignment
204 results, but, as mentioned before, these microbenchmark numbers should
205 not be used as absolutes for determining if an allocator is worth using.
253 in a real world allocation scenario. SQL operations were chosen as a
267 These numbers should be as performant as the current allocator.
279 nearly as performant as the current allocator.
319 on a thread as if it was rerunning the real trace. The only issue is that
344 checked in as zip files.
358 they should not be used as absolute value for comparison against the
359 current allocator. But, they should be in the same range as the current
372 when running the memory traces acts as a proxy for this. An allocator that
400 This is a benchmark that treats the trace data as if all allocations
403 every does an allocation at the same time as another thread.
412 order to get as accurate a number as possible.