Time to debug-brk... our primary perf metric for the node.js users

Starts at: ? (maybe navigationStart)
Ends at: sources panel done loading, with execution paused on first line.


 

We would like to measure the performance for starting up DevTools for node.js users.

We discussed several options:

1. When node.js debugger connection is established (e.g. console shows Node.js Main Context as the target). This essentially measures when the user can interact with the node.js program via the console.
2. File navigator tree view is displayed. Doesn't seem as meaningful as the other metrics.
3. Script is displayed in text editor. Script doesn't get displayed in editor until the first time the debugger pauses
4. For "--debug-brk", when the first statement is paused by debugger. Currently, the front-end doesn't know if it's stopped because of "--debug-brk" so this would require a protocol change. In addition, many users might not be using "--debug-brk".

Given these pros and cons, I will start working on measuring metric #1.