Implement performance benchmarks for idle time spell checker |
|||
Issue descriptionThis is the tracking bug for the instrumentation of performance metrics into idle time spell checker.
,
Apr 20 2017
We already have good UMAs for a finch trial: - SpellCheck.api.async: number of characters in each spell check request - WebCore.ScriptedIdleTaskController.IdleCallbackOverrun: how long an idle task runs overtime So the only remaining task is to implement performance benchmarks. And the priority is lower because the benchmark does not block the launch process: we only need to know the performance gain from benchmarks. Whether the performance gain comes at a price will be found out from finch trial.
,
Sep 6 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by xiaoche...@chromium.org
, Mar 8 2017