Searched refs:numbers (Results 1 – 5 of 5) sorted by relevance
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, the192 single thread numbers from trace data is a better representative of204 results, but, as mentioned before, these microbenchmark numbers should243 As with the other microbenchmarks, an allocator with numbers in the same267 These numbers should be as performant as the current allocator.357 The performance numbers for these runs tend to have a wide variability so
104 there isn't a high variation in the numbers.
1111 std::vector<std::string> numbers = android::base::Split(s, "-"); in TEST() local1112 if (numbers.size() == 1u) { in TEST()1115 online_cpus += atoi(numbers[1].c_str()) - atoi(numbers[0].c_str()) + 1; in TEST()
161 A similar result can be achieved using `taskset`. The first parameter is a bitmask of core numbers
1537 // only supports the old numbers (http://b/141010852).