Add alerts for some bigger wasm perf benchmarks |
|||
Issue descriptionHi Annie, could you please add alerts for the following graphs: internal.client.v8/*/v8/Wasm/AngryBots/* internal.client.v8/*/v8/Unity/*/* internal.client.v8/*/v8/Unity-asm-wasm/*/* Example graphs here: https://chromeperf.appspot.com/report?sid=400cffc9a4f825ddf7b65d94d0083e3ac7e32e473a1e6a545288e9636045091f&start_rev=45158&end_rev=46035 All alerts should be redirected to wasm-perf@google.com and shown on the "V8 Wasm Perf Sheriff" dashboard: https://chromeperf.appspot.com/alerts?sortby=end_revision&sortdirection=down&sheriff=V8%20Wasm%20Perf%20Sheriff Thanks, and let me know if you are missing any information.
,
Jun 22 2017
Thanks! May I ask a follow-up question: We sometimes use the unit "microseconds", for which chromeperf does not know whether upper or lower is better. Is there a list of existing units somewhere? If there is nothing for microseconds: Can this list be extended?
,
Jun 22 2017
+eakuefner, simonhatch FYI Here's the documentation on the dashboard data format, you should be able to set improvement_direction or higher_is_better depending on which format you use: https://github.com/catapult-project/catapult/blob/master/dashboard/docs/data-format.md
,
Jun 26 2017
+machenbach Michael, where does this connect to our v8-perf tests? The output of run_perf.py does not seem to fit the dashboard data format.
,
Jun 26 2017
Damn, forgot to +machenbach.
,
Jun 29 2017
Thanks Michael and Annie, that last issue was fixed yesterday by replacing the unit 'microseconds' by 'us'. |
|||
►
Sign in to add a comment |
|||
Comment 1 by sullivan@chromium.org
, Jun 22 2017