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
  • test_utils
  • ANGLETest.cpp
Find file
BlameHistoryPermalink
  • Jamie Madill's avatar
    D3D11: Use dirty bits for applyVertexBuffers. · abf66fb3
    Jamie Madill authored Aug 23, 2017
    If the vertex array has any dirty or dynamic attribs, we must do an
    update. Similarly, if a prior state change has left the vertex
    state invalidated, we do an update. For instance, a program change
    means we need a new input layout. If there was no such invalidation
    or dirtyness we can skip the call to InputLayoutCache.
    
    This improves the performance of the draw call benchmark (with no
    state changes) by about 50% on the D3D11 null driver. Increases the
    frames per second count of the aquarium demo with the passthrough
    command buffer by about 25% on a test machine.
    
    BUG=angleproject:1156
    
    Change-Id: I8381999029f5b1912030a3342e96285a58f95e82
    Reviewed-on: https://chromium-review.googlesource.com/616784
    Commit-Queue: Jamie Madill <jmadill@chromium.org>
    Reviewed-by: 's avatarGeoff Lang <geofflang@chromium.org>
    abf66fb3
ANGLETest.cpp 28.2 KB
EditWeb IDE
×

Replace ANGLETest.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.