1. 06 Jun, 2016 1 commit
  2. 30 May, 2016 1 commit
  3. 17 May, 2016 1 commit
  4. 27 Apr, 2016 1 commit
  5. 26 Apr, 2016 1 commit
  6. 09 Mar, 2016 1 commit
  7. 07 Mar, 2016 1 commit
  8. 02 Mar, 2016 1 commit
  9. 29 Feb, 2016 1 commit
  10. 12 Dec, 2015 1 commit
  11. 28 Oct, 2015 1 commit
  12. 28 Sep, 2015 1 commit
  13. 18 Sep, 2015 1 commit
  14. 10 Sep, 2015 1 commit
  15. 08 Sep, 2015 1 commit
  16. 26 Jun, 2015 1 commit
  17. 08 Jun, 2015 1 commit
  18. 03 Jun, 2015 1 commit
  19. 01 Jun, 2015 1 commit
  20. 21 May, 2015 1 commit
  21. 19 May, 2015 1 commit
  22. 06 May, 2015 1 commit
  23. 10 Apr, 2015 1 commit
  24. 09 Apr, 2015 1 commit
  25. 23 Mar, 2015 1 commit
  26. 20 Mar, 2015 1 commit
  27. 13 Feb, 2015 1 commit
  28. 10 Feb, 2015 1 commit
  29. 12 Dec, 2014 1 commit
  30. 05 Dec, 2014 1 commit
  31. 04 Dec, 2014 2 commits
    • arv's avatar
      Add js-perf-test for ES6 class default constructor · f515e363
      arv authored
      BUG=v8:3330
      LOG=N
      TBR=dslomov@chromium.org
      
      Review URL: https://codereview.chromium.org/754523004
      
      Cr-Commit-Position: refs/heads/master@{#25669}
      f515e363
    • machenbach's avatar
      Make JSTests ready for Android measurements. · 1364ea7c
      machenbach authored
      This adds a common perf configuration for JSTests including
      Classes, Collections, Iterators and Strings. This allows
      the android test runner to handle subdirectories correctly
      and to share the base.js resource in the parent directory.
      
      The new json config has added resources configs for the
      Android runner.
      
      The perf runner's relative paths on the device are fixed as
      well. Resources are only pushed on the configuration node
      where they are specified. They are pushed to a dir on the
      device that follows the same directory structure as on the
      host. The binary is executed in the benchmark folder on the
      device like on the host to allow relative path file
      loading.
      
      BUG=chromium:374740
      LOG=n
      TEST=python -m unittest run_perf_test
      TBR=ulan@chromium.org
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/779923002
      
      Cr-Commit-Position: refs/heads/master@{#25655}
      1364ea7c
  32. 20 Nov, 2014 3 commits
  33. 29 Oct, 2014 1 commit
    • adamk@chromium.org's avatar
      Add performance tests for Map/Set with String and Object keys · 5b85911e
      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
      5b85911e
  34. 22 Oct, 2014 2 commits
  35. 21 Oct, 2014 1 commit
  36. 17 Oct, 2014 1 commit