Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Issue 2325 in v8: Feature request - DTrace probes for Developers(first!) & Sys Admins :)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
codesite-nore...@google.com  
View profile  
 More options Sep 10 2012, 12:31 pm
From: codesite-nore...@google.com
Date: Mon, 10 Sep 2012 16:31:06 +0000
Local: Mon, Sep 10 2012 12:31 pm
Subject: Re: Issue 2325 in v8: Feature request - DTrace probes for Developers(first!) & Sys Admins :)

Comment #2 on issue 2325 by F.Gallo...@gmail.com: Feature request - DTrace  
probes for Developers(first!) & Sys Admins :)
http://code.google.com/p/v8/issues/detail?id=2325

Yes, Chrome is the leader in performance tools in the browser. It is my  
preferred browser for development. Using Dtrace can offer a deeper level of  
inspection into a developer's application behavior in the v8 runtime, with  
other pieces of software (Java Hotspot, MySQL, Apache) and/or in the  
operating system (disk i/o, filesystem, network, etc).

While it is easy to pick up DTrace concepts and "D" scripting language,  
I've quickly noticed a hurdle of implementing DTrace is a developer's  
knowledge of each specific application, library or kernel module. Those  
best suited for adding the probes are those most familiar with each app or  
module behavior as they know where best to place the probes. I would love  
to contribute but it may be awhile before I am able to do so. In the mean  
time, please take this as my humble suggestion inorder to open up a  
discussion.

I'd like to see:
1. DTrace probes added to v8 (and other parts of chrome)
2. The ability in Chrome developer tools to access DTrace
     - Webkit could add probes too.
3. Users are able to create chrome extensions for realtime visualizations  
of DTrace data
     - DTrace currently does require root access to use, which may be a  
problem
     - I'm very impressed with the visualizations Joyent (SmartOS) and Apple  
XCode Instruments have been able to achieve using DTrace (and can be used  
safely on production systems!!)

Visualization examples:
http://dtrace.org/blogs/brendan/2012/03/26/subsecond-offset-heat-maps/
http://dtrace.org/blogs/brendan/2012/02/12/visualizing-process-execut...
http://blog.nodejs.org/2012/04/25/profiling-node-js/

Other DTrace Benefits:
- Enhances Debugging
     - Joyent has been able to find performance issues and bugs in numerous  
applications that they do NOT develop internally
    - can reduce time finding performance issues in any level of the OS.
    - http://dtrace.org/blogs/brendan/2012/08/09/10-performance-wins/

- Inspect other parts of your software stack
      - Java, Ruby and other Dynamic languages (running locally)
      - MySQL,Apache

- Developer Education
   - learn kenral module behavior
   - patterns in latency
   - teach about v8 behavior using D scripts and visualizations


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.