New issue
Advanced search Search tips

Issue 596402 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

v8_execution metrics should measure cpu time, not wall time

Project Member Reported by jochen@chromium.org, Mar 21 2016

Issue description

this should help to reduce the variance
 

Comment 1 by cbruni@chromium.org, Mar 21 2016

I guess we should have both.

Real-world user perceived time is wall-time not CPU time, so we should definitely keep that in the spirit of real-world benchmarks.

Comment 2 by jochen@chromium.org, Mar 21 2016

yeah, having both is fine.

Comment 3 by cbruni@chromium.org, Apr 18 2016

Status: WontFix (was: Assigned)
As discussed with fmeawad a while ago: using cpu time doesn't help much with reducing noise.

Comment 4 by jochen@chromium.org, Apr 18 2016

hum, now that we actually have cpu time, the noise in my graphs is down to an acceptable level.

before, i got a bimodal distribution, depending on whether the v8 execution or something else that happens during load got descheduled.

Comment 5 by cbruni@chromium.org, Apr 18 2016

Status: Assigned (was: WontFix)
oh ok :) then let's keep this open.

Comment 6 by jochen@chromium.org, Apr 18 2016

Status: Fixed (was: Assigned)
well, with tbmv2 it's actually fixed :)

Sign in to add a comment