1. 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
  2. 31 Mar, 2009 1 commit
  3. 27 Mar, 2009 1 commit
  4. 25 Mar, 2009 1 commit
  5. 26 Feb, 2009 1 commit
  6. 24 Feb, 2009 1 commit
  7. 23 Feb, 2009 1 commit
  8. 20 Feb, 2009 1 commit
  9. 18 Feb, 2009 3 commits
  10. 17 Feb, 2009 1 commit
  11. 03 Feb, 2009 1 commit
  12. 19 Dec, 2008 1 commit
    • christian.plesner.hansen@gmail.com's avatar
      Added support in the profiler for creating 'regions' that cover part · d7c933e7
      christian.plesner.hansen@gmail.com authored
      of the generated code.  These can be used by the profiler to
      categorize the ticks that occur within generated code and thereby show
      more detailed information about where time is spent in generated code.
      For instance, this is what the profiler displayed for a simple regexp
      benchmark with irregexp-native before:
      
      [JavaScript]:
         total  nonlib   name
         87.2%   87.2%   RegExp: (?:\w*\W+)*
      
      This is what we can display now:
      
      [JavaScript]:
         total  nonlib   name
         87.2%   87.2%   RegExp: (?:\w*\W+)*
                         -  53.0%  56.7% BranchOrBacktrack
                         -  14.9%  59.8% CheckCharacterLT
                         -  13.7%  20.4% CheckStackLimit
                         -   6.7%   6.7% SafeCall
                         -   2.7%   7.0% CheckCharacterGT
                         -   2.4%   2.4% SafeReturn
                         -   2.1%   2.1% LoadCurrentCharacter
                         -   1.8%   1.8% PushRegister
                         -   0.9%   0.9% PopRegister
                         -   0.9%   0.9% AdvanceRegister
                         -   0.3%   0.3% PopCurrentPosition
                         -   0.3%   0.3% CheckGreedyLoop
                         -   0.0%  20.4% PushBacktrack
                         -   0.0%  22.3% CheckCharacter
                         -   0.0%   2.4% IfRegisterLT
      
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1010 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      d7c933e7
  13. 10 Oct, 2008 1 commit
  14. 09 Sep, 2008 1 commit
  15. 03 Sep, 2008 1 commit