1. 18 Dec, 2013 1 commit
  2. 18 Oct, 2013 1 commit
  3. 14 Oct, 2013 1 commit
  4. 10 Oct, 2013 1 commit
  5. 11 Sep, 2013 1 commit
  6. 05 Sep, 2013 1 commit
  7. 02 Sep, 2013 1 commit
  8. 29 Aug, 2013 1 commit
  9. 28 Aug, 2013 6 commits
  10. 27 Aug, 2013 1 commit
  11. 07 Aug, 2013 1 commit
  12. 06 Aug, 2013 1 commit
  13. 05 Aug, 2013 3 commits
  14. 30 Jul, 2013 1 commit
    • yurys@chromium.org's avatar
      Simplify sampling rate calculation · 6ba502fa
      yurys@chromium.org authored
      Sampling rate is now calculated as total number of samples divided by profiling time in ms. Before the patch the sampling rate was updated once per 100ms which doesn't have any obvious advantage over the simpler method.
      
      Also we are going to get rid of the profile node self and total time calculation in the v8 CPU profiler and only expose profiling start/end time for CpuProfile and number of ticks on each ProfileNode and let clients do all the math should they need it.
      
      BUG=None
      R=bmeurer@chromium.org, loislo@chromium.org
      
      Review URL: https://codereview.chromium.org/21105003
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@15944 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      6ba502fa
  15. 06 Jul, 2013 1 commit
  16. 02 Jul, 2013 3 commits
  17. 01 Jul, 2013 6 commits
  18. 26 Jun, 2013 3 commits
  19. 03 Jun, 2013 1 commit
  20. 14 May, 2013 1 commit
    • yurys@chromium.org's avatar
      Skip samples where top function's stack frame is not setup properly · 69c2f54d
      yurys@chromium.org authored
      Stack iterator takes return address based on the frame pointer (ebp) and detects JS frames based on value at fp + StandardFrameConstants::kMarkerOffset. So in order the iterator to work correctly this values should be already setup for the current function. Stack frame is constructed at the very beginning of JS function code and destroyed before return. If sample is taken before before the frame construction is completed or after it was destroyed the stack iterator will wrongly think that FP points at the current functions frame base and will skip callers frame. To avoid this we mark code ranges where  stack frame doesn't exist and completely ignore such samples.
      
      This fixes cctest/test-cpu-profiler/CollectCpuProfile flakiness.
      
      BUG=v8:2628
      R=jkummerow@chromium.org
      
      Review URL: https://codereview.chromium.org/14253015
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@14670 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      69c2f54d
  21. 26 Apr, 2013 1 commit
  22. 24 Apr, 2013 1 commit
  23. 02 Apr, 2013 1 commit
  24. 21 Mar, 2013 1 commit