1. 27 Sep, 2018 1 commit
  2. 31 Aug, 2018 1 commit
    • Bret Sepulveda's avatar
      profview: View source code of functions with samples inline. · b9cb78a7
      Bret Sepulveda authored
      If profiling is done with --log-source-code profview will now display
      a "View source" link for each function in the tree view. Clicking this
      will show a new source viewer, with sampled lines highlighted. See the
      associated bug for screenshots.
      
      This patch also fixes a bug in the profiler where the source info of
      only the first code object for each function would be logged, and
      includes some refactoring.
      
      Bug: v8:6240
      Change-Id: Ib96a9cfc54543d0dc9bef4657cdeb96ce28b223c
      Reviewed-on: https://chromium-review.googlesource.com/1194231
      Commit-Queue: Bret Sepulveda <bsep@chromium.org>
      Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55542}
      b9cb78a7
  3. 24 Aug, 2018 1 commit
  4. 10 Aug, 2017 1 commit
  5. 28 Jul, 2017 1 commit
  6. 25 Apr, 2017 1 commit
  7. 22 Mar, 2017 1 commit
  8. 21 Mar, 2017 1 commit
    • leszeks's avatar
      [tools] Manually write JSON in profile.js to avoid huge strings · 0956e587
      leszeks authored
      In the tick processor, in cases where there are a lot of ticks (e.g.
      long running programs), JSON.stringify could throw a range exception
      because the created string is too large.
      
      Instead of creating the entire JSON string in memory, we now write the
      top-level parts of the JSON manually, writing out the ticks individually
      instead of all together.
      
      Review-Url: https://codereview.chromium.org/2754683002
      Cr-Commit-Position: refs/heads/master@{#43973}
      0956e587
  9. 04 Mar, 2017 1 commit
  10. 20 Jan, 2015 1 commit
    • jkummerow's avatar
      Profiler improvements · feffccca
      jkummerow authored
      (1) --prof-cpp: Collects ticks like --prof, but ignores code creation events to reduce distortion (so all JS ticks will be "unaccounted"). Useful for profiling C++ code.
      (2) --timed-range flag for tick processor: Ignores ticks before the first and after the last call to Date.now(). Useful for focusing on the timed section of a test.
      
      Review URL: https://codereview.chromium.org/802333002
      
      Cr-Commit-Position: refs/heads/master@{#26168}
      feffccca
  11. 17 Oct, 2014 1 commit
  12. 12 Sep, 2011 2 commits
  13. 13 Jul, 2011 1 commit
  14. 22 Feb, 2011 1 commit
    • mikhail.naganov@gmail.com's avatar
      Fix CPU profiling for Crankshaft. · 56788625
      mikhail.naganov@gmail.com authored
      The main issue was due to multiple recompilations of functions.  Now
      code objects are grouped by function using SFI object address.
      JSFunction objects are no longer tracked, instead we track SFI object
      moves. To pick a correct code version, we now sample return addresses
      instead of JSFunction addresses.
      
      tools/{linux|mac|windows}-tickprocessor scripts differentiate
      between code optimization states for the same function
      (using * and ~ prefixes introduced earlier).
      
      DevTools CPU profiler treats all variants of function code as
      a single function.
      
      ll_prof treats each optimized variant as a separate entry, because
      it can disassemble each one of them.
      
      tickprocessor.py not updated -- it is deprecated and will be removed.
      
      BUG=v8/1087,b/3178160
      TEST=all existing tests pass, including Chromium layout tests
      
      Review URL: http://codereview.chromium.org/6551011
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6902 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      56788625
  15. 10 Feb, 2011 1 commit
  16. 21 Jan, 2010 1 commit
    • mikhail.naganov@gmail.com's avatar
      Fix issue 553: function frame is skipped in profile when compare stub is called. · 999e3fca
      mikhail.naganov@gmail.com authored
      The problem appeared due to a fact that stubs doesn't create a stack
      frame, reusing the stack frame of the caller function. When building
      stack traces, the current function is retrieved from PC, and its
      callees are retrieved by traversing the stack backwards. Thus, for
      stubs, the stub itself was discovered via PC, and then stub's caller's
      caller was retrieved from stack.
      
      To fix this problem, a pointer to JSFunction object is now captured
      from the topmost stack frame, and is saved into stack trace log
      record. Then a simple heuristics is applied whether a referred
      function should be added to decoded stack, or not, to avoid reporting
      the same function twice (from PC and from the pointer.)
      
      BUG=553
      TEST=added to mjsunit/tools/tickprocessor
      
      Review URL: http://codereview.chromium.org/546089
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3673 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      999e3fca
  17. 18 Jan, 2010 1 commit
    • mikhail.naganov@gmail.com's avatar
      Fix issue 571: display descriptive names for code objects from snapshot. · 37d39724
      mikhail.naganov@gmail.com authored
      As this is only needed for internal profiling (not for DevTools),
      the following approach had been chosen:
      
       - during snapshot creation, positions of serialized objects inside
         a snapshot are logged;
      
       - then during V8 initialization, positions of deserealized objects
         are logged;
      
       - those positions are used for retrieving code objects names from
         snapshot creation log, which needs to be supplied to tick processor
         script.
      
      Positions logging is controlled with the new flag: --log_snapshot_positions.
      This flag is turned off by default, and this adds no startup penalty.
      
      To plug this fix to Golem, the following actions are needed:
      
       - logs created using 'mksnapshot' need to be stored along with VM images;
      
       - tick processor script needs to be run with '--snapshot-log=...' cmdline
         argument.
      
      BUG=571
      
      Review URL: http://codereview.chromium.org/551062
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3635 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      37d39724
  18. 14 Jul, 2009 1 commit
  19. 30 Apr, 2009 1 commit
  20. 27 Apr, 2009 1 commit
    • mikhail.naganov@gmail.com's avatar
      TickProcessor script reimplemented in JavaScript. · aa2c3312
      mikhail.naganov@gmail.com authored
      This is an effort to reuse profiler data processing code both in
      TickProcessor and Dev Tools Profiler. The old Python implementation
      will be removed.
      
      The new TickProcessor works almost identical to the previous one.
      However, it has some differences:
      
      1. Not very useful "Call profile" section is replaced with a new
         WebKit-like "Bottom up (heavy) profile" which shows the most
         expensive functions together with their callers. I used it
         personally in order to find and remove bottlenecks in the
         tickprocessor script itself, and found it quite helpful.
      
      2. Code entries with duplicate names (they occur for RegExes, stubs
         and sometimes for anonymous Function objects) are now distinguished
         by adding an occurence number inside curly brackets.
      
      3. (Address -> code entry) mapping is more precise in boundary cases.
      
      4. Windows version no more requires specifying .map file location.
      
      5. Works faster.
      
      Review URL: http://codereview.chromium.org/99054
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1802 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      aa2c3312
  21. 24 Apr, 2009 1 commit
  22. 17 Apr, 2009 1 commit