1. 19 Apr, 2013 1 commit
  2. 16 Apr, 2013 3 commits
  3. 15 Apr, 2013 1 commit
  4. 12 Apr, 2013 1 commit
  5. 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
  6. 21 Mar, 2013 1 commit
  7. 07 Mar, 2013 1 commit
  8. 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
  9. 15 Feb, 2013 1 commit
  10. 14 Dec, 2012 1 commit
  11. 30 Nov, 2012 1 commit
  12. 26 Nov, 2012 1 commit
  13. 16 Nov, 2012 1 commit
  14. 22 Oct, 2012 1 commit
  15. 18 Oct, 2012 1 commit
  16. 17 Oct, 2012 1 commit
  17. 02 Oct, 2012 1 commit
  18. 01 Oct, 2012 1 commit
  19. 27 Sep, 2012 1 commit
  20. 17 Sep, 2012 1 commit
  21. 22 Aug, 2012 2 commits
  22. 10 Jul, 2012 1 commit
  23. 21 May, 2012 1 commit
  24. 13 Apr, 2012 1 commit
  25. 30 Mar, 2012 1 commit
    • danno@chromium.org's avatar
      Fix performance regressions due to lazy initialization. · 63f03357
      danno@chromium.org authored
      This CL:
      - Adds a new trait parameter to LazyInstance to let it initialize the instance
        without paying the cost of atomic operations (which are expensive on Mac).
        This only works for users who don't care about thread-safety and this is now
      the default initialization trait used by LazyInstance in v8.
      
      - Reverts the changes that were made in r11010 in isolate.{cc,h}. That lets
        Isolate's accessors be as cheap as they were before (but adds one static initializer).
      
      - Adds OS::PostSetup() used to initialize the math functions which depend on CPU features.
      That lets the math functions get rid of CallOnce().
      
      BUG=118686
      
      Review URL: https://chromiumcodereview.appspot.com/9873023
      Patch from Philippe Liard <pliard@chromium.org>.
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11198 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      63f03357
  26. 12 Mar, 2012 2 commits
  27. 05 Mar, 2012 1 commit
  28. 02 Mar, 2012 2 commits
  29. 23 Feb, 2012 1 commit
  30. 24 Jan, 2012 1 commit
  31. 17 Jan, 2012 2 commits
  32. 16 Jan, 2012 1 commit
  33. 13 Jan, 2012 1 commit
  34. 02 Dec, 2011 1 commit