Add performance.mark()s around each test step
authorcommit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 18 Jul 2017 23:22:46 +0000 (23:22 +0000)
committercommit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 18 Jul 2017 23:22:46 +0000 (23:22 +0000)
commit2a28a6c714f5b7881a41d7db29ed36a48e3963a4
tree8b5f0903af8b6f2159b0503289855052a367b746
parent19f007441e5792804fe42229f9ab520b87c4abd1
Add performance.mark()s around each test step
https://bugs.webkit.org/show_bug.cgi?id=174530

Patch by Matt Kotsenas <mattkot@microsoft.com> on 2017-07-18
Reviewed by Ryosuke Niwa.

Add `performance.mark()` around each test step to make analysis
simpler. Now each test step can be investigated via dev tools, ETW, etc.

* Speedometer/resources/benchmark-runner.js:
(BenchmarkRunner.prototype._writeMark):
(BenchmarkRunner.prototype._runTest):
(BenchmarkRunner.prototype._runTestAndRecordResults):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@219640 268f45cc-cd09-0410-ab3c-d52691b4dbfc
PerformanceTests/ChangeLog
PerformanceTests/Speedometer/resources/benchmark-runner.js