Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
A
angle
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • angle
  • Repository

Switch branch/tag
  • angle
  • src
  • tests
  • perf_tests
  • TracePerfTest.cpp
Find file
BlameHistoryPermalink
  • Jamie Madill's avatar
    Trace Tests: Run one step per frame. · 8b76d37f
    Jamie Madill authored Nov 17, 2020
    Instead of trying to make one step take one sequence of frames,
    one run step per frame always. This will scale better for traces
    that are very long and cannot complete in the short times we use
    on the bots.
    
    Adds an explicit step round-up feature so that we can always run
    chunks of full trace sequences when we are not running with a
    fixed maximum number of steps.
    
    Bug: b/172977194
    Change-Id: I0f069a66a86d8c4a698ebffb66782d13843539a5
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2545884Reviewed-by: 's avatarCody Northrop <cnorthrop@google.com>
    Reviewed-by: 's avatarCourtney Goeltzenleuchter <courtneygo@google.com>
    Commit-Queue: Jamie Madill <jmadill@chromium.org>
    8b76d37f
TracePerfTest.cpp 28.6 KB
EditWeb IDE
×

Replace TracePerfTest.cpp

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.