Searched refs:benchmark (Results 1 – 6 of 6) sorted by relevance
/cts/suite/cts/utils/ |
D | grapher.py | 44 for benchmark in tests: 45 if benchmark.startswith('com.android.cts.opengl.primitive'): 46 results = tests[benchmark] 51 plt.title(benchmark[benchmark.index('#') + 1:])
|
/cts/tests/openglperf2/jni/primitive/ |
D | GLPrimitive.cpp | 79 JNIEnv* env, jclass /*clazz*/, jobject surface, jint benchmark, in Java_android_opengl2_cts_primitive_GLPrimitiveActivity_setupBenchmark() argument 82 switch (benchmark) { in Java_android_opengl2_cts_primitive_GLPrimitiveActivity_setupBenchmark() 97 "Unknown benchmark '%d'", benchmark); in Java_android_opengl2_cts_primitive_GLPrimitiveActivity_setupBenchmark()
|
/cts/tests/openglperf2/src/android/opengl2/cts/primitive/ |
D | GLPrimitiveBenchmark.java | 121 private void runBenchmark(BenchmarkName benchmark, boolean offscreen, int numFrames, in runBenchmark() argument 123 String benchmarkName = benchmark.toString(); in runBenchmark()
|
D | GLPrimitiveActivity.java | 106 Surface surface, int benchmark, boolean offscreen); in setupBenchmark() argument
|
/cts/hostsidetests/sustainedperf/dhrystone/ |
D | Rationale | 12 The Dhrystone benchmark program [1] has become a popular benchmark for 15 satisfies a need for an easy-to-use integer benchmark; it gives a first 19 With the increasing use of the benchmark, it seems necessary to 20 reconsider the benchmark and to check whether it can still fulfill this 57 critical remarks on the benchmark - I agree with several of them - and 59 benchmark into something different from what has become known as 61 outweight the benefits. If I were to write a new benchmark program, I 65 always be encouraged to use more than just one benchmark. 71 Readers who want to use the benchmark for their own measurements can 100 execution of the benchmark. [all …]
|
D | Drystone-2.1.sh | 28 XThe Dhrystone benchmark program [1] has become a popular benchmark for 77 Xoutweight the benefits. If I were to write a new benchmark program, I
|