[meta] Performance measurements for mus+chrome |
||||||||||
Issue descriptionThis is the tracking bug for all performance related tasks (measurements, fixes) for mus and mus+chrome. ⛆ |
|
|
,
Aug 25 2017
,
Sep 19 2017
,
Jan 3 2018
Removing as a blocker for 731255 and instead we'll track the time it takes for events to be processed (798775) as well as time to initial present (792214).
,
Feb 26 2018
,
Aug 15
,
Nov 8
,
Nov 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5e499839825f764882f9166fe6e401eefb020a90 commit 5e499839825f764882f9166fe6e401eefb020a90 Author: Scott Violet <sky@chromium.org> Date: Mon Nov 12 20:58:26 2018 chromeos: make EventInjector reset time/latecy when injecting This way telemetry only includes the time from ash, not the initial hop from browser to ash. BUG=759163 TEST=none Change-Id: I65f514d6bee3346a7b828b431300e5cf3277d521 Reviewed-on: https://chromium-review.googlesource.com/c/1327416 Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#607320} [modify] https://crrev.com/5e499839825f764882f9166fe6e401eefb020a90/services/ws/event_injector.cc [modify] https://crrev.com/5e499839825f764882f9166fe6e401eefb020a90/ui/events/event.h |
|||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by sadrul@chromium.org
, Aug 25 2017