1. 12 Oct, 2018 1 commit
  2. 11 Sep, 2018 1 commit
  3. 03 Aug, 2018 1 commit
  4. 22 Jun, 2018 1 commit
  5. 30 Nov, 2017 1 commit
  6. 09 Oct, 2017 1 commit
  7. 10 Jul, 2017 1 commit
  8. 13 Feb, 2017 1 commit
  9. 16 Dec, 2016 1 commit
  10. 04 Nov, 2016 1 commit
  11. 03 Nov, 2016 2 commits
  12. 08 Sep, 2016 1 commit
  13. 05 Sep, 2016 1 commit
    • fmeawad's avatar
      [RuntimeCallStats] Move tracing runtime instrumentation closer to the original version. · e5ba156d
      fmeawad authored
      After we landed the tracing runtime call stats, which gave
      us a lot of V8 insight in tracing, we noticed that there is
      some arising issues and discrepancies.
      
      Issues include:
      Missing trace events, that happened due to
      transforming those trace events into runtime calls
      
      Discrepancies include:
      Missing categories in Runtime call stats like GC,
      because we are not handling the Scoped runtime calls
      properly in the tracing version.
      
      To reduce/eliminate those issue, we are taking a small
      step back. We are unifying the RuntimeStats code and
      using the original one. That would allow us to use all
      the original probes but emit trace events from them.
      We are also putting back the trace-events in their place.
      
      The output from both system should be intact (Except of
      the addition of the missing trace-events).
      
      Also as a byproduct, we are reducing the number of context
      scopes by half since we are using the same scope as
      runtime call stats.
      
      As a follow up to this CL, we will address the non-scoped
      Runtime Call Stats (mainly in GC).
      BUG=642373
      
      Review-Url: https://codereview.chromium.org/2296243002
      Cr-Commit-Position: refs/heads/master@{#39180}
      e5ba156d
  14. 10 Aug, 2016 1 commit
  15. 08 Aug, 2016 1 commit
  16. 05 Aug, 2016 1 commit
  17. 03 Aug, 2016 4 commits
  18. 19 Jul, 2016 1 commit
  19. 14 Jul, 2016 1 commit
  20. 11 May, 2016 1 commit
  21. 06 Apr, 2016 1 commit
    • cbruni's avatar
      [runtime] reduce runtime function and builtins overhead · ceb14f8c
      cbruni authored
      All the counters, trace events and runtime call stats roughly create a 30%
      overhead when calling into the runtime. This CL factors out the counters into
      separate non-inlined functions. This way we can reduce the overhead to a
      minimum and still have some useful stats without a compile-time flag.
      
      BUG=chromium:596055
      LOG=n
      
      Review URL: https://codereview.chromium.org/1868513002
      
      Cr-Commit-Position: refs/heads/master@{#35308}
      ceb14f8c
  22. 11 Mar, 2016 1 commit
  23. 10 Mar, 2016 1 commit
  24. 09 Mar, 2016 1 commit
  25. 08 Mar, 2016 1 commit
  26. 23 Feb, 2016 1 commit
    • cbruni's avatar
      [counters] Making runtime counters reentrant. · 5e468666
      cbruni authored
      So far counters did not work when they were reentrant and thus would lead to
      wrong bookkeeping of the counter stack. Using a separate stack-allocated linked
      list to track the timer stack solves this issue. This is a temporary workaround
      with the limitations of the counter system in mind. Eventually we will move to
      the trace-based system for these kind of statistics.
      
      BUG=v8:4770
      LOG=n
      
      Review URL: https://codereview.chromium.org/1695733002
      
      Cr-Commit-Position: refs/heads/master@{#34208}
      5e468666
  27. 11 Feb, 2016 4 commits
  28. 09 Feb, 2016 3 commits
  29. 08 Feb, 2016 2 commits
  30. 22 Jan, 2016 1 commit
    • jarin's avatar
      Runtime call counters and timers. · 747bd6f2
      jarin authored
      In d8, run with --runtime-call-stats and it will output the stats when d8 finishes.
      
      In Chrome, run the following: (only on trusted code, this punches *massive* security hole into Chrome)
      
      chrome --js-flags="--runtime-call-stats --allow-natives-syntax"
      
      To get the stats in the console, just run
      
      console.log(%GetAndResetRuntimeCallStats());
      
      To output stats every second:
      
      setInterval(function() { console.log(%GetAndResetRuntimeCallStats()); }, 1000)
      
      Review URL: https://codereview.chromium.org/1615943002
      
      Cr-Commit-Position: refs/heads/master@{#33462}
      747bd6f2