tree: d0acd3435973e7c21d2bd8e254edd43df19e2deb [path history] [tgz]
  1. third_party/
  2. ANGLEPerfTest.cpp
  3. ANGLEPerfTest.h
  4. ANGLEPerfTestArgs.cpp
  5. ANGLEPerfTestArgs.h
  6. BindingPerf.cpp
  7. BitSetIteratorPerf.cpp
  8. BlitFramebufferPerf.cpp
  9. BufferSubData.cpp
  10. ClearPerf.cpp
  11. CompilerPerf.cpp
  12. DispatchComputePerf.cpp
  13. DrawCallPerf.cpp
  14. DrawCallPerfParams.cpp
  15. DrawCallPerfParams.h
  16. DrawElementsPerf.cpp
  17. DynamicPromotionPerfTest.cpp
  18. EGLInitializePerf.cpp
  19. EGLMakeCurrentPerf.cpp
  20. FramebufferAttachmentPerfTest.cpp
  21. GenerateMipmapPerf.cpp
  22. glmark2Benchmark.cpp
  23. IndexConversionPerf.cpp
  24. IndexDataManagerTest.cpp
  25. InstancingPerf.cpp
  26. InterleavedAttributeData.cpp
  27. LinkProgramPerfTest.cpp
  28. MapBufferRange.cpp
  29. MultisampledRenderToTexturePerf.cpp
  30. MultisampledSwapchainResolve.cpp
  31. MultiviewPerf.cpp
  32. PointSprites.cpp
  33. PreRotationPerf.cpp
  34. README.md
  35. ResultPerf.cpp
  36. TextureSampling.cpp
  37. TexturesPerf.cpp
  38. TextureUploadPerf.cpp
  39. TracePerfTest.cpp
  40. UniformsPerf.cpp
  41. VertexArrayPerfTest.cpp
  42. VulkanBarriersPerf.cpp
  43. VulkanCommandBufferPerf.cpp
  44. VulkanPipelineCachePerf.cpp
src/tests/perf_tests/README.md

ANGLE Performance Tests

angle_perftests is a standalone testing suite that contains targeted tests for OpenGL, Vulkan and ANGLE internal classes. The tests currently run on the Chromium ANGLE infrastructure and report results to the Chromium perf dashboard.

You can also build your own dashboards. For example, a comparison of ANGLE's back-end draw call performance on Windows NVIDIA can be found at this link. Note that this link is not kept current.

Running the Tests

You can follow the usual instructions to check out and build ANGLE. Build the angle_perftests target. Note that all test scores are higher-is-better. You should also ensure is_debug=false in your build. Running with angle_assert_always_on or debug validation enabled is not recommended.

Variance can be a problem when benchmarking. We have a test harness to run a single test in an infinite loop and print some statistics to help mitigate variance. See scripts/perf_test_runner.py. To use the script first compile angle_perftests into a folder with the word Release in it. Then provide the name of the test as the argument to the script. The script will automatically pick up the most current angle_perftests and run in an infinite loop.

Choosing the Test to Run

You can choose individual tests to run with --gtest_filter=*TestName*. To select a particular ANGLE back-end, add the name of the back-end to the test filter. For example: DrawCallPerfBenchmark.Run/gl or DrawCallPerfBenchmark.Run/d3d11. Many tests have sub-tests that run slightly different code paths. You might need to experiment to find the right sub-test and its name.

Null/No-op Configurations

ANGLE implements a no-op driver for OpenGL, D3D11 and Vulkan. To run on these configurations use the gl_null, d3d11_null or vulkan_null test configurations. These null drivers will not do any GPU work. They will skip the driver entirely. These null configs are useful for diagnosing performance overhead in ANGLE code.

Command-line Arguments

Several command-line arguments control how the tests run:

  • --one-frame-only: Runs tests once and quickly exits. Used as a quick smoke test.
  • --enable-trace: Write a JSON event log that can be loaded in Chrome.
  • --trace-file file: Name of the JSON event log for --enable-trace.
  • --calibration: Prints the number of steps a test runs in a fixed time. Used by perf_test_runner.py.
  • --steps-per-trial x: Fixed number of steps to run for each test trial.
  • --max-steps-performed x: Upper maximum on total number of steps for the entire test run.
  • --screenshot-dir dir: Directory to store test screenshots. Implies --save-screenshots. On Android this directory is on device, not local (see also --render-test-output-dir). Only implemented in TracePerfTest.
  • --save-screenshots: Save screenshots. Only implemented in TracePerfTest.
  • --screenshot-frame <frame>: Which frame to capture a screenshot of. Defaults to first frame (1). Only implemented in TracePerfTest.
  • --render-test-output-dir=dir: Directory to store test artifacts (including screenshots but unlike --screenshot-dir, dir here is always a local directory regardless of platform and --save-screenshots isn't implied).
  • --verbose: Print extra timing information.
  • --warmup-loops x: Number of times to warm up the test before starting timing. Defaults to 3.
  • --warmup-steps x: Maximum number of steps for the warmup loops. Defaults to unlimited.
  • --no-warmup: Skip warming up the tests. Equivalent to --warmup-steps 0.
  • --calibration-time: Run each test calibration step in a fixed time. Defaults to 1 second.
  • --max-trial-time x: Run each test trial under this max time. Defaults to 10 seconds.
  • --fixed-test-time x: Run the tests until this much time has elapsed.
  • --trials: Number of times to repeat testing. Defaults to 3.
  • --no-finish: Don't call glFinish after each test trial.
  • --enable-all-trace-tests: Offscreen and vsync-limited trace tests are disabled by default to reduce test time.
  • --minimize-gpu-work: Modify API calls so that GPU work is reduced to minimum.
  • --validation: Enable serialization validation in the trace tests. Normally used with SwiftShader and retracing.
  • --perf-counters: Additional performance counters to include in the result output. Separate multiple entries with colons: ‘:’.

For example, for an endless run with no warmup, run:

angle_perftests --gtest_filter=TracePerfTest.Run/vulkan_trex_200 --steps 1000000 --no-warmup

The command line arguments implementations are located in ANGLEPerfTestArgs.cpp.

Test Breakdown

  • DrawCallPerfBenchmark: Runs a tight loop around DrawArarys calls.
    • validation_only: Skips all rendering.
    • render_to_texture: Render to a user Framebuffer instead of the default FBO.
    • vbo_change: Applies a Vertex Array change between each draw.
    • tex_change: Applies a Texture change between each draw.
  • UniformsBenchmark: Tests performance of updating various uniforms counts followed by a DrawArrays call.
    • vec4: Tests vec4 Uniforms.
    • matrix: Tests using Matrix uniforms instead of vec4.
    • multiprogram: Tests switching Programs between updates and draws.
    • repeating: Skip the update of uniforms before each draw call.
  • DrawElementsPerfBenchmark: Similar to DrawCallPerfBenchmark but for indexed DrawElements calls.
  • BindingsBenchmark: Tests Buffer binding performance. Does no draw call operations.
    • 100_objects_allocated_every_iteration: Tests repeated glBindBuffer with new buffers allocated each iteration.
    • 100_objects_allocated_at_initialization: Tests repeated glBindBuffer the same objects each iteration.
  • TexSubImageBenchmark: Tests glTexSubImage update performance.
  • BufferSubDataBenchmark: Tests glBufferSubData update performance.
  • TextureSamplingBenchmark: Tests Texture sampling performance.
  • TextureBenchmark: Tests Texture state change performance.
  • LinkProgramBenchmark: Tests performance of glLinkProgram.
  • glmark2: Runs the glmark2 benchmark.
  • TracePerfTest: Runs replays of restricted traces, not available publicly. To enable, read more in RestrictedTraceTests

Many other tests can be found that have documentation in their classes.

Understanding the Metrics

  • cpu_time: Amount of CPU time consumed by an iteration of the test. This is backed by GetProcessTimes on Windows, getrusage on Linux/Android, and zx_object_get_info on Fuchsia.
    • This value may sometimes be larger than wall_time. That is because we are summing up the time on all CPU threads for the test.
  • wall_time: Wall time taken to run a single iteration, calculated by dividing the total wall clock time by the number of test iterations.
    • For trace tests, each rendered frame is an iteration.
  • gpu_time: Estimated GPU elapsed time per test iteration. We compute the estimate using GLES timestamp queries at the beginning and ending of each test loop.
    • For trace tests, this metric is only enabled in vsync mode.