forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Save EventMetrics to report after processing is done
Currently, as soon as we notice a frame needs to be produced while processing an event, a copy of its EventMetrics is saved for reporting. The plan is to add the timestamp of when the processing of the event is done (on both compositor and main threads) to this object to be included in reports. To allow this, the copy of the object should be saved after the processing is done and the timestamp is added. This CL changes EventsMetricsManager to get a callback for its scoped monitor instead of a pointer to the metrics object. The callback will be called when the scoped monitor is destroyed (i.e. when the event processing is finished). The client code can update metrics object as appropriate and return it to EventsMetricsManager if necessary. Also, if the metrics object is supposed to be saved, the client code can safely move the object to EventsMetricsManager as it won't need it anymore. Bug: 1054009 Change-Id: I503bf64171f08f8233d7f738304b0e2e3a96da31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488549 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Jonathan Ross <jonross@chromium.org> Commit-Queue: Mohsen Izadi <mohsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#823583}
- Loading branch information
Mohsen Izadi
authored and
Commit Bot
committed
Nov 3, 2020
1 parent
ae52b2a
commit eb1682c
Showing
16 changed files
with
233 additions
and
98 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.