v8/test/js-perf-test/Modules
Jakob Kummerow 693e8ac59f [js-perf-tests] Fix Modules benchmarks
The score is computed based on how often the benchmark's function can
be run within one second. Simply importing a Module repeatedly doesn't
do any work, so to make the test score meaningful, we must wrap the
payload into a function that can be called explicitly for every run.

NOTRY=true

Bug: v8:1569
Change-Id: Iadaed6df1f1652d8860271e327c505f0b8f20c2d
Reviewed-on: https://chromium-review.googlesource.com/639396
Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
Reviewed-by: Adam Klein <adamk@chromium.org>
Reviewed-by: Georg Neis <neis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#47686}
2017-08-29 16:50:44 +00:00
..
basic-export.js [js-perf-tests] Fix Modules benchmarks 2017-08-29 16:50:44 +00:00
basic-import.js [js-perf-tests] Fix Modules benchmarks 2017-08-29 16:50:44 +00:00
basic-namespace.js [js-perf-tests] Fix Modules benchmarks 2017-08-29 16:50:44 +00:00
run.js [js-perf-tests] Fix Modules benchmarks 2017-08-29 16:50:44 +00:00
value.js [js-perf-tests] Add more property accesses to module namespace micro-benchmark 2017-08-24 23:56:08 +00:00