Skip to content

Commit 6a61f69

Browse files
Trottfhemberger
authored andcommitted
copyedit profiling guide
1 parent 1618ebd commit 6a61f69

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

locale/en/docs/guides/simple-profiling.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -133,13 +133,13 @@ passwords, or inside the Express framework itself.
133133

134134
Since we ran our application using the --prof option, a tick file was generated
135135
in the same directory as your local run of the application. It should have the
136-
form isolate-0x124353456789-v8.log. In order to make sense of this file, we need
137-
to use the tick processor included in the Node.js source at
138-
<nodejs_dir>/tools/v8-prof/tick-processor.js. It is important that the version
139-
of the tick-processor that you run comes from the same version of node source as
140-
version of node used to generate the isolate file. This will no longer be a
141-
concern when the tick processor is [installed by default][]. The raw tick output
142-
can be processed using this tool by running:
136+
form `isolate-0xnnnnnnnnnnnn-v8.log` (where `n` is a digit). In order to make
137+
sense of this file, we need to use the tick processor included in the Node.js
138+
source at `<nodejs_dir>/tools/v8-prof/tick-processor.js`. It is important that
139+
the version of the tick-processor comes from the source for the version of node
140+
used to generate the isolate file. (This will no longer be a concern when the
141+
tick processor is [installed by default][].) The raw tick output can be
142+
processed using this tool by running:
143143

144144
```
145145
node <path_to_nodejs_src>/tools/v8-prof/tick-processor.js isolate-0x101804c00-v8.log >processed.txt

0 commit comments

Comments
 (0)