1. 02 Jul, 2018 1 commit
  2. 08 Jun, 2018 1 commit
  3. 24 May, 2018 1 commit
  4. 16 May, 2018 1 commit
  5. 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
  6. 05 Apr, 2018 1 commit
  7. 02 Mar, 2018 1 commit
  8. 01 Mar, 2018 1 commit
  9. 19 Feb, 2018 1 commit
  10. 17 Feb, 2018 2 commits
  11. 06 Feb, 2018 2 commits
  12. 24 Jan, 2018 1 commit
  13. 12 Jan, 2018 1 commit
  14. 08 Jan, 2018 1 commit
  15. 18 Dec, 2017 1 commit
  16. 15 Dec, 2017 2 commits
  17. 11 Dec, 2017 1 commit
  18. 08 Dec, 2017 1 commit
  19. 04 Dec, 2017 1 commit
  20. 30 Nov, 2017 2 commits
  21. 29 Nov, 2017 1 commit
  22. 28 Nov, 2017 1 commit
  23. 23 Nov, 2017 1 commit
  24. 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
  25. 15 Nov, 2017 1 commit
  26. 14 Nov, 2017 3 commits
    • Leszek Swirski's avatar
      [compiler] Add new "no cache reason" enum values · 61e04e28
      Leszek Swirski authored
      Add enum values to the "no cache reason" API which reflect new types of
      no-cache reason we will want to distinguish.
      
      Also, renames one of the enum values (BecauseExtension ->
      BecauseV8Extension) because it was confusing. It's a V8-only type of no
      cache reason, so it shouldn't affect embedders.
      
      Bug: chromium:769203
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I41d4ecfb35b2e91b71562b4f23b15d20f16a943c
      Reviewed-on: https://chromium-review.googlesource.com/769010Reviewed-by: 's avatarMythri Alle <mythria@chromium.org>
      Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49367}
      61e04e28
    • Ross McIlroy's avatar
      [compiler] Add background compilation mode. · 9a4b334f
      Ross McIlroy authored
      Adds support for compiling top-level code on a background thread behind a flag.
      When the flag is enabled, any background-parsing-task will perform compilation
      as well as parsing.
      
      BUG=v8:5203
      TBR=marja@chromium.org,mstarzinger@chromium.org
      
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: Icf90ac7211298d3555515dafc7c3245618ec1304
      Reviewed-on: https://chromium-review.googlesource.com/764048
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49364}
      9a4b334f
    • Camillo Bruni's avatar
      [RCS] Add explicit tests for function callbacks · 6526c6dd
      Camillo Bruni authored
      This CL adds a very crude unittest to check that RuntimeCallStats work
      correctly with api callbacks present. This currently doesn't check that
      all parent timers (namely FunctionCallback) are handled properly.
      
      Drive-by-Fix:
      - Use Microseconds for all RCS timer tests
      - Add TestWithContext::SetGlobalProperty helper
      - Use explicit v8:: prefix in test-utils.{h,cc}
      
      Change-Id: I054e78abca0b87a3b9e07d3b06cccdad15403bae
      Reviewed-on: https://chromium-review.googlesource.com/766429
      Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49348}
      6526c6dd
  27. 10 Nov, 2017 2 commits
  28. 07 Nov, 2017 3 commits
  29. 06 Nov, 2017 2 commits
  30. 03 Nov, 2017 1 commit