[webkit-changes] [WebKit/WebKit] b84e32: [JS3] Use performance instead of Date for timing w...

[Keith Miller]

  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: b84e32b70debb71660f7b258e841f42a2c13746e
      https://github.com/WebKit/WebKit/commit/b84e32b70debb71660f7b258e841f42a2c13746e
  Author: Keith Miller <keith_miller at apple.com>
  Date:   2024-08-08 (Thu, 08 Aug 2024)

  Changed paths:
    M PerformanceTests/JetStream3/JetStreamDriver.js
    M PerformanceTests/JetStream3/cli.js

  Log Message:
  -----------
  [JS3] Use performance instead of Date for timing where available
https://bugs.webkit.org/show_bug.cgi?id=277771
rdar://133411753

Reviewed by Yusuke Suzuki.

performance.now has less clamping than Date.now in some browsers when COOP/COEP headers are set.
Thus gives a more accurate timing for the benchamrk so we should use performance.now instead.

* PerformanceTests/JetStream3/JetStreamDriver.js:
(Driver.prototype.async start):
(Driver.prototype.runCode):
(Driver.prototype.prepareToRun.text.div):
(prototype.get runnerCode):
(prototype.async run):
(AsyncBenchmark.get runnerCode.return.async doRun):
(AsyncBenchmark.prototype.get runnerCode):
(AsyncBenchmark):
* PerformanceTests/JetStream3/cli.js:
(async runJetStream):

Canonical link: https://commits.webkit.org/281992@main



To unsubscribe from these emails, change your notification settings at https://github.com/WebKit/WebKit/settings/notifications