WebXR: use fence status change time for timing
Using wallclock time for render completion can overestimate GPU usage if the fence client wait is called on an already-completed fence. Use the fence status change time instead to get a more accurate measurement. It's technically best-effort, with fallback to wallclock time, but in practice seems to be reliably available. Bug: 1136276 Change-Id: I29c2830220de1dbac053cfeec8e4494f6d2eb42e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461959 Auto-Submit: Klaus Weidner <klausw@chromium.org> Commit-Queue: Klaus Weidner <klausw@chromium.org> Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Reviewed-by:Piotr Bialecki <bialpio@chromium.org> Cr-Commit-Position: refs/heads/master@{#815241}
Showing
Please register or sign in to comment