v8/test/js-perf-test/Array
Jakob Kummerow 6dd3fbe40f [js-perf-test] Fewer number-to-string conversions in Array benchmarks
Some of the Array benchmarks were unintentionally spending a lot of
time on Number-to-String conversions. This patch avoids that, by
computing the dynamically-created strings only once.

Bug: chromium:1240981
Change-Id: If10826813d555398b45c22c958dee27e17f35d3c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3106747
Reviewed-by: Michael Stanton <mvstanton@chromium.org>
Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
Cr-Commit-Position: refs/heads/main@{#76387}
2021-08-19 11:27:35 +00:00
..
copy-within.js
every.js
filter.js
find-index.js [js-perf-test] Fewer number-to-string conversions in Array benchmarks 2021-08-19 11:27:35 +00:00
find.js [js-perf-test] Fewer number-to-string conversions in Array benchmarks 2021-08-19 11:27:35 +00:00
for-each.js [js-perf-test] Fewer number-to-string conversions in Array benchmarks 2021-08-19 11:27:35 +00:00
from.js Add non-COW inputs to Array.from benchmarks. 2018-11-02 11:41:06 +00:00
join.js
map.js [js-perf-test] Fewer number-to-string conversions in Array benchmarks 2021-08-19 11:27:35 +00:00
of.js
reduce-right.js [js-perf-test] Fewer number-to-string conversions in Array benchmarks 2021-08-19 11:27:35 +00:00
reduce.js [js-perf-test] Fewer number-to-string conversions in Array benchmarks 2021-08-19 11:27:35 +00:00
run.js [js-perf-test] Fewer number-to-string conversions in Array benchmarks 2021-08-19 11:27:35 +00:00
slice.js [benchmarks] Move Array slice benchmarks to js-perf-test 2019-05-20 09:05:52 +00:00
some.js
to-string.js