Skip to content

V
V8
Switch branch/tag
  1. 03 Aug, 2017 1 commit
  3. 31 Jul, 2017 1 commit
  5. 28 Jul, 2017 1 commit
  7. 19 Jul, 2017 1 commit
  9. 14 Jul, 2017 1 commit
  11. 13 Jul, 2017 1 commit
  13. 05 Jul, 2017 2 commits
  15. 04 Jul, 2017 1 commit
  17. 20 Jun, 2017 1 commit
  19. 19 Jun, 2017 1 commit
  21. 14 Jun, 2017 1 commit
  23. 09 Jun, 2017 1 commit
  25. 05 Jun, 2017 1 commit
  27. 26 May, 2017 1 commit
  29. 22 May, 2017 2 commits
  31. 16 May, 2017 1 commit
  33. 26 Apr, 2017 1 commit
  35. 25 Apr, 2017 1 commit
  37. 24 Apr, 2017 1 commit
  39. 19 Apr, 2017 1 commit
    • bmeurer's avatar
      [js-perf-test] Add microbenchmarks for materialized rest parameters. · 07e163bd
      bmeurer authored 
      Functions that take mandatory parameters plus a number of optional
parameters, that need to be materialized as an Array are quite common.
The simplest possible case of this is essentially:

  function foo(mandatory, ...args) { return args; }

Babel translates this to something like:

  function foo(mandatory) {
    "use strict";
    for (var _len = arguments.length,
             args = Array(_len > 1 ? _len - 1 : 0),
             _key = 1; _key < _len; _key++) {
      args[_key - 1] = arguments[_key];
    }
    return args;
  }

The key to great performance here is to make sure that we don't
materialize the (unmapped) arguments object in this case, plus that we
have some kind of fast-path for the Array constructor and the
initialization loop.

This microbenchmark ensures that we have decent performance even in the
case where the assignment to args is polymorphic, i.e. the arguments
have seen different elements kinds, starting with FAST_HOLEY_ELEMENTS
and then FAST_HOLEY_SMI_ELEMENTS.

R=yangguo@chromium.org
BUG=v8:6262

Review-Url: https://codereview.chromium.org/2823343004
Cr-Commit-Position: refs/heads/master@{#44709}
      07e163bd
  41. 12 Apr, 2017 1 commit
  43. 11 Apr, 2017 1 commit
  45. 31 Mar, 2017 1 commit
  47. 29 Mar, 2017 1 commit
  49. 24 Mar, 2017 1 commit
  51. 22 Mar, 2017 2 commits
  53. 21 Mar, 2017 2 commits
  55. 09 Mar, 2017 1 commit
  57. 24 Feb, 2017 1 commit
  59. 15 Feb, 2017 1 commit
  61. 10 Feb, 2017 1 commit
  63. 06 Feb, 2017 1 commit
  65. 09 Jan, 2017 1 commit
  67. 20 Dec, 2016 1 commit
    • jgruber's avatar
      [js-perf-test] Add a basic async-await microbenchmark · 9feefafa
      jgruber authored 
      These benchmarks are intended to compare the overhead of async-await vs.
a naive promise implementation vs. the babel async-await transformation.
The functions in the benchmark don't do any work themselves, so results
should reflect only overhead of the chosen implementation.

Current numbers on my local machine (higher is better):

BaselineES2017-AsyncAwait(Score): 2006
BaselineNaivePromises-AsyncAwait(Score): 7470
Native-AsyncAwait(Score): 3640

BUG=v8:5639

Review-Url: https://codereview.chromium.org/2577393002
Cr-Commit-Position: refs/heads/master@{#41860}
      9feefafa
  69. 05 Dec, 2016 1 commit
  71. 24 Nov, 2016 1 commit