- 16 Nov, 2017 1 commit
-
-
peterwmwong authored
- Add {Map/Set/WeakMap/WeakSet}-Constructor microbenchmarks - Add {Map/Set}-Double microbenchmarks (testing heap number keys) Bug: v8:6604 Change-Id: Icadd5c81bfb59a58a2a65e119663d3f22637165d Reviewed-on: https://chromium-review.googlesource.com/773595Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#49398}
-
- 19 Oct, 2017 1 commit
-
-
Jaroslav Sevcik authored
Change-Id: I1157ef6baaf60bdbf5d55a1b8f75edb15794baef Bug: v8:6916 Reviewed-on: https://chromium-review.googlesource.com/715800Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#48724}
-
- 29 Oct, 2014 1 commit
-
-
adamk@chromium.org authored
The big change here is to split out each key type into its own benchmark suite, since optimizations for different key types are likely to be disjoint. ForEach tests have also been split into separate "Iteration" suites, again with the thought that iteration performance is likely separable from key type. As part of adding the new tests, rejiggered the existing tests: - Map.set and Set.add (along with their Weak variants) no longer include construction costs in their scores - Moved key logic into the shared common.js R=arv@chromium.org, machenbach@chromium.org Review URL: https://codereview.chromium.org/685753004 Cr-Commit-Position: refs/heads/master@{#24969} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24969 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-