Release Notes

Jump to bottom Edit New page

Parashuram N edited this page Jun 15, 2015 · 5 revisions

1.3.0

Better error messages on the CLI
Metric Name Change meanFrameTime is now called meanFrameTime_rafto better reflect its source and avoid confusion from mean_frame_time that is calculated using tracing metrics
Added more Navigation Timing metrics which are simpler to undertand

1.2.9

Added a new set of metrics using Network Resource Timing API

1.2.8

CLI metrics now in sorted in order of importance
Re-enabled RuntimePerfMetrics
Fixed minor bugs

1.2.5

Chrome 42 now uses tracing for timeline events also, so using this new format to collect timeline data.
RunTimePerfMetrics were disabled to make a quick fix available.

1.2.2

When ChromeTracingMetrics was moved to pick up metrics from performance logs, it was double counting browser render process. This was a MAJOR fix in this release, and now gives more accurate frame rates.

1.0.0

Removed GpuBenchmarkingProbe.js
[Breaking Change] Metrics are now simple numbers. More details are available using the docs API
[Breaking Change] NavTimingMetrics and ChromeTimelineMetrics renamed