Index: tools/turbolizer/README.md |
diff --git a/tools/turbolizer/README.md b/tools/turbolizer/README.md |
index 61f006ed44cea1638b89d0d6677491beb804ac0c..54e1051690ff2f089af71be951e0dceef4010d2e 100644 |
--- a/tools/turbolizer/README.md |
+++ b/tools/turbolizer/README.md |
@@ -15,10 +15,10 @@ the turbolizer directory, e.g.: |
python -m SimpleHTTPServer 8000 |
Optionally, profiling data generated by the perf tools in linux can be merged |
-with the .json files using the perf-turbo.py file included. The following |
+with the .json files using the turbolizer-perf.py file included. The following |
command is an example of using the perf script: |
- perf script -i perf.data.jitted -s perf-turbo.py turbo-main.json |
+ perf script -i perf.data.jitted -s turbolizer-perf.py turbo-main.json |
The output of the above command is a json object that can be piped to a file |
which, when uploaded to turbolizer, will display the event counts from perf next |
@@ -50,7 +50,7 @@ The basic example of generating the required data is as follows: |
perf record -k mono /path/to/d8 --turbo --trace-turbo --perf-prof main.js |
perf inject -j -i perf.data -o perf.data.jitted |
- perf script -i perf.data.jitted -s perf-turbo.py turbo-main.json |
+ perf script -i perf.data.jitted -s turbolizer-perf.py turbo-main.json |
These commands combined will run and profile d8, merge the output into a single |
'perf.data.jitted' file, then take the event data from that and link them to the |