1. 16 Aug, 2019 1 commit
  2. 12 Jul, 2019 2 commits
  3. 04 Jul, 2019 2 commits
  4. 01 Jul, 2019 3 commits
  5. 28 Jun, 2019 1 commit
    • Frank Tang's avatar
      Add benchmark for regexp "gi". · b9e1c2c4
      Frank Tang authored
      Measure speed regression of a range of char in complex regexp
      The measurement is using the code from chromium:977003
      
      To measure
      python -u tools/run_perf.py --binary-override-path  out/x64.release/d8 \
        test/js-perf-test/RegExp.json
      
      Run on three setting:
      a. m74 based on tag 7.4.301
      b. trunk (m77)
      c. apply cl 1674851 on trunk
      
      ComplexCaseInsensitiveTest-RegExp
      Score is better if higher
      		Score	imp %	comp to m74
      m74		22910
      		23430
      		23360
      Trunk (m77)	15190	66.30%
      		15710	67.05%
      		15570	66.65%
      CL 1674851	24590	161.88%	107.33%
      		24690	157.16%	105.38%
      		24200	155.43%	103.60%
      
      Bug: chromium:977003
      
      Change-Id: I7756f4739c44a07949103650565d1ca902e1b7ca
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1679651Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Frank Tang <ftang@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62449}
      b9e1c2c4
  6. 25 Jun, 2019 1 commit
  7. 24 Jun, 2019 1 commit
  8. 17 Jun, 2019 1 commit
  9. 13 Jun, 2019 1 commit
  10. 12 Jun, 2019 1 commit
  11. 11 Jun, 2019 2 commits
  12. 06 Jun, 2019 1 commit
  13. 05 Jun, 2019 1 commit
  14. 03 Jun, 2019 1 commit
  15. 30 May, 2019 1 commit
  16. 24 May, 2019 3 commits
    • Simon Zünd's avatar
      Reland "[array] Move Array#sort pre-processing to Torque" · 843b6646
      Simon Zünd authored
      This is a reland of 2b0ac2fb
      
      The layout test that caused this revert was fixed with:
      https://crrev.com/c/1627386
      
      Original change's description:
      > [array] Move Array#sort pre-processing to Torque
      >
      > This CL removes the "PrepareElementsForSort" runtime function, and
      > replaces it with a simpler version in Torque. The biggest difference
      > is that certain sparse configurations no longer have a fast-path.
      >
      > The Torque pre-processing step replaces the existing Torque mechanism that
      > copied already pre-processed elements into the "work" FixedArray. The Torque
      > compacting works as follows:
      >   - Iterate all elements from 0 to {length}
      >     - If the element is the hole: Do nothing.
      >     - If the element is "undefined": Increment undefined counter.
      >     - In all other cases, push the element into the "work" FixedArray.
      >
      > Then the "work" FixedArray is sorted as before. Writing the elements from
      > the "work" array back into the receiver, after sorting, has three steps:
      >   1. Copy the sorted elements from the "work" FixedArray to the receiver.
      >   2. Add previously counted number of "undefined" to the receiver.
      >   3. Depending on the backing store either delete properties or
      >      set them to the Hole up to {length}.
      >
      > Bug: v8:8714
      > Change-Id: I14eccb7cfd2e4618bce2a85cba0689d7e0380ad2
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1619756
      > Commit-Queue: Simon Zünd <szuend@chromium.org>
      > Reviewed-by: Tobias Tebbi <tebbi@chromium.org>
      > Reviewed-by: Jakob Gruber <jgruber@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#61812}
      
      TBR: jgruber@chromium.org
      Bug: v8:8714
      Change-Id: If7613f6e5f37c5e0d649e8192195594bc6c32100
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627977
      Commit-Queue: Simon Zünd <szuend@chromium.org>
      Auto-Submit: Simon Zünd <szuend@chromium.org>
      Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61827}
      843b6646
    • Simon Zünd's avatar
      Revert "[array] Move Array#sort pre-processing to Torque" · 70eeb22d
      Simon Zünd authored
      This reverts commit 2b0ac2fb.
      
      Reason for revert: Breaks scrollingcoordinator/non-fast-scrollable-region-nested.html layout test on https://ci.chromium.org/p/v8/builders/ci/V8-Blink%20Linux%2064/32241 
      
      Original change's description:
      > [array] Move Array#sort pre-processing to Torque
      > 
      > This CL removes the "PrepareElementsForSort" runtime function, and
      > replaces it with a simpler version in Torque. The biggest difference
      > is that certain sparse configurations no longer have a fast-path.
      > 
      > The Torque pre-processing step replaces the existing Torque mechanism that
      > copied already pre-processed elements into the "work" FixedArray. The Torque
      > compacting works as follows:
      >   - Iterate all elements from 0 to {length}
      >     - If the element is the hole: Do nothing.
      >     - If the element is "undefined": Increment undefined counter.
      >     - In all other cases, push the element into the "work" FixedArray.
      > 
      > Then the "work" FixedArray is sorted as before. Writing the elements from
      > the "work" array back into the receiver, after sorting, has three steps:
      >   1. Copy the sorted elements from the "work" FixedArray to the receiver.
      >   2. Add previously counted number of "undefined" to the receiver.
      >   3. Depending on the backing store either delete properties or
      >      set them to the Hole up to {length}.
      > 
      > Bug: v8:8714
      > Change-Id: I14eccb7cfd2e4618bce2a85cba0689d7e0380ad2
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1619756
      > Commit-Queue: Simon Zünd <szuend@chromium.org>
      > Reviewed-by: Tobias Tebbi <tebbi@chromium.org>
      > Reviewed-by: Jakob Gruber <jgruber@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#61812}
      
      TBR=peter.wm.wong@gmail.com,jgruber@chromium.org,tebbi@chromium.org,szuend@chromium.org
      
      Change-Id: If1c1bc07f38dfbd4bf6b6ce8f9d70714e7526877
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:8714
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627976Reviewed-by: 's avatarSimon Zünd <szuend@chromium.org>
      Commit-Queue: Simon Zünd <szuend@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61814}
      70eeb22d
    • Simon Zünd's avatar
      [array] Move Array#sort pre-processing to Torque · 2b0ac2fb
      Simon Zünd authored
      This CL removes the "PrepareElementsForSort" runtime function, and
      replaces it with a simpler version in Torque. The biggest difference
      is that certain sparse configurations no longer have a fast-path.
      
      The Torque pre-processing step replaces the existing Torque mechanism that
      copied already pre-processed elements into the "work" FixedArray. The Torque
      compacting works as follows:
        - Iterate all elements from 0 to {length}
          - If the element is the hole: Do nothing.
          - If the element is "undefined": Increment undefined counter.
          - In all other cases, push the element into the "work" FixedArray.
      
      Then the "work" FixedArray is sorted as before. Writing the elements from
      the "work" array back into the receiver, after sorting, has three steps:
        1. Copy the sorted elements from the "work" FixedArray to the receiver.
        2. Add previously counted number of "undefined" to the receiver.
        3. Depending on the backing store either delete properties or
           set them to the Hole up to {length}.
      
      Bug: v8:8714
      Change-Id: I14eccb7cfd2e4618bce2a85cba0689d7e0380ad2
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1619756
      Commit-Queue: Simon Zünd <szuend@chromium.org>
      Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61812}
      2b0ac2fb
  17. 23 May, 2019 1 commit
  18. 20 May, 2019 1 commit
  19. 15 May, 2019 3 commits
  20. 11 May, 2019 1 commit
  21. 07 May, 2019 1 commit
  22. 04 May, 2019 1 commit
    • Sergiy Belozorov's avatar
      [tools] Default to 4 retries for all perf tests · b3e2bcf9
      Sergiy Belozorov authored
      Overall, total test runtime that was wasted due to timeouts is 3420 seconds in
      the last 2 weeks. Even with 4 retries, assuming all of them time out, needed
      additional capacity is under 2 hours per week. Based on this analysis, I think
      it's safe to land this CL.
      
      Note that this is not intended as a long-term solution of the timeout problem,
      but rather a temporary solution to prevent ongoing errors. Proper investigation
      and correct long-term solution are still needed and tracked in the bug.
      
      R=machenbach@chromium.org, tmrts@chromium.org
      
      Bug: chromium:841700
      Change-Id: Id16e6b784fa85bb9e28ed8c6b267b583636e2dc1
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1593342Reviewed-by: 's avatarTamer Tas <tmrts@chromium.org>
      Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61224}
      b3e2bcf9
  23. 30 Apr, 2019 1 commit
  24. 25 Apr, 2019 2 commits
  25. 16 Apr, 2019 1 commit
  26. 12 Apr, 2019 1 commit
  27. 25 Mar, 2019 1 commit
  28. 21 Mar, 2019 2 commits
  29. 20 Mar, 2019 1 commit