New issue
Advanced search Search tips

Issue 723704 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
ericrk@chromium.org
enne@chromium.org
senorblanco@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Investigate remaining problems for MotionMark > Focus benchmark

Project Member Reported by vmi...@chromium.org, May 17 2017 
Chrome Version: 59.0.3068.0

There are a couple of things we should try to fix that affect the Focus benchmark.

1) On platforms other than Mac (with CoreAnimation) we seem to have a high overhead from running glFlush() for every filter.  I think this is the one in GLRenderer::DrawRPDQ(), and I suspect we could remove this.

2) The Focus test itself bottlenecks in Javascript computing the property prefix ('Webkit') all the time.

focus.js:59, FocusElement.animate() calls Utilities.setElementPrefixedProperty(), which computes a prefix in Utilities.browserPrefix().

This needs a patch for the benchmark code in WebKit.
Project Member

Comment 1 by sheriffbot@chromium.org, May 18 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by reve...@chromium.org, Jun 1 2018

Status: Available (was: Untriaged)
►

Sign in to add a comment