ESlint-bridge profiling

This tool allows identifying the bottlenecks of a rule performance.

Fetch dependencies

Run: npm i

Chrome dev tools

The Chrome dev tools allow you to see what functions took how much CPU time as:

• a top-down tree
• a bottom-up tree
• a (flame) graph

1. Boot the server in debug mode: npm run server. (or npm run compile-server if you have modifications in the TS source code)
2. Open dev tools on chrome, using F12
3. You should see a green NodeJS icon like that, click it to connect the dev tools to the server's debugger:

4. You might need to make sure the server starts by going to the "sources" tab and pressing the "play" button
5. In the server logs, you should see that the server is listening
6. Select the "Profiler" tab
7. Select "Profiles" on the left
8. Press "Start" on the bottom

7. Launch the Analysis on ruling projects: npm run profile <my-rule-id> <ts|all> <parallelism>
   1. ts for TS-only projects, all for both JS and TS, JS-only by default.
   2. parallelism sets the number of parallel files sent to the bridge for analysis. Defaults to 5.
8. Press "Stop"
9. View the profile
10. Change the view from "Heavy (Bottom Up)" to "Tree (Top Down)" (on the top menu, above "Self Time")

11. If you prefer, you can also select the "Chart" view to display a flame graph

Links

• Chrome profiling
• Chrome profiling - views
• Flame graphs with 0x
• NodeJS profiling