New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 749012 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

blink_perf.css taking 49 minutes on reference build (was 16 minutes)

Project Member Reported by nedngu...@google.com, Jul 26 2017

Issue description

This benchmark is now taking 49 minutes on reference build & 26 minutes on TOT build. In total, this cycle time is too much for a micro benchmark.

See this graph for the cycle time growth:
https://chromeperf.appspot.com/report?sid=a1dc602a0812f1e086f691f15948aeb5f8952d54e8eec77ce55e8bdffcfc559a&rev=487872 

nainar@ is it possible to reduce the cycle time here?
 
Cc: shend@chromium.org
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 26 2017

Labels: Hotlist-Google
Project Member

Comment 3 by bugdroid1@chromium.org, Jul 27 2017

Comment 4 by shend@chromium.org, Jul 27 2017

Status: Fixed (was: Assigned)
Should be fixed now as the graph has gone back down.
Cc: -shend@chromium.org nainar@chromium.org
Owner: shend@chromium.org
The ref build still takes a lot 43 minutes (mean we improve css perf a lot, which is good!). The next thing for us is probably to update the ref build.

Thanks shend!

Sign in to add a comment