New issue
Advanced search Search tips

Issue 699335 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Task

Blocking:
issue 671922



Sign in to add a comment

Implement performance benchmarks for idle time spell checker

Project Member Reported by xiaoche...@chromium.org, Mar 8 2017

Issue description

This is the tracking bug for the instrumentation of performance metrics into idle time spell checker.
 
Layout test editing/spelling/spelling-huge-text.html tests performance rather than functionality.

We should convert it to a performance test.
Labels: -Pri-1 Pri-2
Summary: Implement performance benchmarks for idle time spell checker (was: Instrument performance metrics into idle time spell checker)
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.
Status: WontFix (was: Assigned)

Sign in to add a comment