Skip to content

V
V8
Switch branch/tag
  1. 05 Sep, 2013 1 commit
  3. 04 Sep, 2013 1 commit
  5. 02 Sep, 2013 1 commit
  7. 29 Aug, 2013 2 commits
  9. 28 Aug, 2013 9 commits
  11. 26 Aug, 2013 1 commit
  13. 31 Jul, 2013 1 commit
  15. 30 Jul, 2013 1 commit
  17. 29 Jul, 2013 2 commits
  19. 26 Jul, 2013 1 commit
  21. 10 Jul, 2013 1 commit
  23. 20 Jun, 2013 1 commit
  25. 19 Apr, 2013 1 commit
  27. 16 Apr, 2013 3 commits
  29. 15 Apr, 2013 1 commit
  31. 12 Apr, 2013 1 commit
  33. 10 Apr, 2013 1 commit
    • yurys@chromium.org's avatar
      Add sanity test for CPU profiler · c7ce87f8
      yurys@chromium.org authored 
      The new test checks full CPU profiling cycle: using public
V8 API it starts profiling, executes a script, stops profiling
and analyzes collected profile to check that its top-down
tree has expected strutcture. The script that is being profiled
is guaranteed to run > 200ms to make sure enough samples
are collected.

To avoid possible flakiness due to non-deterministic time required
to start new thread on varios OSs when Sampler and ProfilerEventsProcessor
threads are being started the main thread is blocked until the threads
are running.

Also I removed the heuristic in profile-generator.cc where we try
to figure out if the value on top of the sampled stack is return address
of some frameless stub invocation. The code periodically gives false positive
with the new test ending up in an extra node in the collected cpu profile.
After discussion with jkummerow@ we concluded that the logic is too fragile
and that we can address frameless stub invocations in a more reliable way
later should they have a noticeable effect on cpu profiling.

BUG=None

Review URL: https://codereview.chromium.org/13627002

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@14205 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      c7ce87f8
  35. 21 Mar, 2013 1 commit
  37. 07 Mar, 2013 1 commit
  39. 26 Feb, 2013 1 commit
    • yurys@chromium.org's avatar
      Send SIGPROF signals on the profiler event processor thread · dc9b8176
      yurys@chromium.org authored 
      The patch is based on the previous one that was rolled out: https://code.google.com/p/v8/source/detail?r=12985

On Linux sampling for CPU profiler is initiated on the profiler event processor thread, other platforms to follow.

CPU profiler continues to use SamplingCircularQueue, we will replave it with a single sample buffer when Mac and Win ports support profiling on the event processing thread.

When --prof option is specified profiling is initiated either on the profiler event processor thread if CPU profiler is on or on the  SignalSender thread as it used to if no CPU profiles are being collected.

ProfilerEventsProcessor::ProcessEventsAndDoSample now waits in a tight loop, processing collected samples until sampling interval expires. To save CPU resources I'm planning to change that to use nanosleep as only one sample is expected in the queue at any point.

BUG=v8:2364

Review URL: https://codereview.chromium.org/12321046

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13735 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      dc9b8176
  41. 15 Feb, 2013 1 commit
  43. 14 Dec, 2012 1 commit
  45. 30 Nov, 2012 1 commit
  47. 26 Nov, 2012 1 commit
  49. 16 Nov, 2012 1 commit
  51. 22 Oct, 2012 1 commit
  53. 18 Oct, 2012 1 commit
  55. 17 Oct, 2012 1 commit