1. 04 Sep, 2018 1 commit
  2. 28 Aug, 2018 3 commits
  3. 22 Aug, 2018 1 commit
    • Camillo Bruni's avatar
      Reland "[runtime] Improve for-in performance" · 827e6d12
      Camillo Bruni authored
      This is a reland of 8fa7f9ed
      
      Original change's description:
      > [runtime] Improve for-in performance
      > 
      > - Add fast-path String conversion for Smi (which is the most common case)
      >   This improves for-in by ~10% on non-initialized enum-caches
      > - Don't use the NumberStringCache for large indices to not overflow the cache
      >   during key collection. This improves worst-case performance by ~2.5x
      > - Drop number_to_string_native and number_to_string_runtime counters
      > 
      > Bug: v8:7717
      > Change-Id: Ic1ff385e3374e6a7e7e7bdb9ae75fb8c238105d1
      > Reviewed-on: https://chromium-review.googlesource.com/1167049
      > Reviewed-by: Toon Verwaest <verwaest@chromium.org>
      > Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      > Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#55233}
      
      Bug: v8:7717
      Change-Id: Ie29041b20ca4a06b8e74a4378e7c1118373072ae
      Reviewed-on: https://chromium-review.googlesource.com/1183721
      Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55316}
      827e6d12
  4. 21 Aug, 2018 1 commit
    • Aseem Garg's avatar
      Revert "[runtime] Improve for-in performance" · a4235f00
      Aseem Garg authored
      This reverts commit 8fa7f9ed.
      
      Reason for revert: Speculating that this breaks GC stress
      
      Original change's description:
      > [runtime] Improve for-in performance
      > 
      > - Add fast-path String conversion for Smi (which is the most common case)
      >   This improves for-in by ~10% on non-initialized enum-caches
      > - Don't use the NumberStringCache for large indices to not overflow the cache
      >   during key collection. This improves worst-case performance by ~2.5x
      > - Drop number_to_string_native and number_to_string_runtime counters
      > 
      > Bug: v8:7717
      > Change-Id: Ic1ff385e3374e6a7e7e7bdb9ae75fb8c238105d1
      > Reviewed-on: https://chromium-review.googlesource.com/1167049
      > Reviewed-by: Toon Verwaest <verwaest@chromium.org>
      > Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      > Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#55233}
      
      TBR=ulan@chromium.org,cbruni@chromium.org,verwaest@chromium.org
      
      Change-Id: I8d0332478afcd7c6a3f8fbf1f044b9aa870b6b13
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:7717
      Reviewed-on: https://chromium-review.googlesource.com/1182676Reviewed-by: 's avatarAseem Garg <aseemgarg@chromium.org>
      Commit-Queue: Aseem Garg <aseemgarg@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55241}
      a4235f00
  5. 20 Aug, 2018 1 commit
  6. 06 Aug, 2018 1 commit
  7. 17 Jul, 2018 1 commit
  8. 13 Jul, 2018 1 commit
  9. 05 Jul, 2018 1 commit
  10. 02 Jul, 2018 1 commit
  11. 08 Jun, 2018 1 commit
  12. 24 May, 2018 1 commit
  13. 16 May, 2018 1 commit
  14. 24 Apr, 2018 1 commit
    • Eric Holk's avatar
      [wasm] Add metrics for Wasm memory allocation · 45dd38c1
      Eric Holk authored
      This adds two new UMA histograms to give us more insight into Wasm
      memory allocation.
      
      The first records the result of every attempt to to allocate a Wasm
      backing store. This will let us know things like how often we
      explicitly trigger a GC, or how often we hit our address space limit.
      
      The second records how many megabytes of address space Wasm reserves.
      A sample is added every time the number either increases or decreases.
      This metric will give us a sense of how many outstanding Wasm memories
      there are in typical usage.
      
      Change-Id: I38c1bc1ad915c26b6cda3c373ededdd395193a4c
      Reviewed-on: https://chromium-review.googlesource.com/1024646
      Commit-Queue: Eric Holk <eholk@chromium.org>
      Reviewed-by: 's avatarDeepti Gandluri <gdeepti@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52767}
      45dd38c1
  15. 05 Apr, 2018 1 commit
  16. 02 Mar, 2018 1 commit
  17. 01 Mar, 2018 1 commit
  18. 19 Feb, 2018 1 commit
  19. 17 Feb, 2018 2 commits
  20. 06 Feb, 2018 2 commits
  21. 24 Jan, 2018 1 commit
  22. 12 Jan, 2018 1 commit
  23. 08 Jan, 2018 1 commit
  24. 18 Dec, 2017 1 commit
  25. 15 Dec, 2017 2 commits
  26. 11 Dec, 2017 1 commit
  27. 08 Dec, 2017 1 commit
  28. 04 Dec, 2017 1 commit
  29. 30 Nov, 2017 2 commits
  30. 29 Nov, 2017 1 commit
  31. 28 Nov, 2017 1 commit
  32. 23 Nov, 2017 1 commit
  33. 17 Nov, 2017 1 commit
    • Leszek Swirski's avatar
      [code-cache] Log resources with no cache handler · 25820bda
      Leszek Swirski authored
      Add another entry to the NoCacheReason enum, reporting that the chromium
      ScriptResource has no cache handler.
      
      Also, the amount of chromium-specific entries in this enum is getting
      too high. So, added a TODO for removing them -- possibly in the future
      we want to do this no-cache reason logging in Chromium after all,
      propagating isolate cache hits and consume failures back up the API with
      an out parameter.
      
      Bug: chromium:769203
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I63ca863cfef61e04e7104318eb79810796b61a9c
      Reviewed-on: https://chromium-review.googlesource.com/776893Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49458}
      25820bda
  34. 15 Nov, 2017 1 commit