Skip to content

Commit 2845d76

Browse files
authored
Update performance tracing details and usage example
1 parent 55b4798 commit 2845d76

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

defender-endpoint/run-analyzer-macos-linux.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -319,7 +319,7 @@ The files generated when using this mode:
319319
320320
#### Collect performance info
321321
322-
Collect extensive machine performance tracing for analysis of a performance scenario that can be reproduced on demand.
322+
Collect extensive machine performance tracing of MDE processes for analysis of a performance scenario that can be reproduced on demand.
323323
324324
```console
325325
-h, --help show this help message and exit
@@ -328,7 +328,20 @@ Collect extensive machine performance tracing for analysis of a performance scen
328328
--length LENGTH length of time to collect (in seconds)
329329
```
330330
331-
Usage example: `sudo ./MDESupportTool performance --frequency 2`
331+
Usage example: `sudo ./MDESupportTool performance --frequency 500`
332+
333+
The files generated when using this mode:
334+
| File | Remarks |
335+
| ------------- | ------------- |
336+
| perf_benchmark.tar.gz | MDE processes performance data |
337+
> [!NOTE]
338+
> The files corresponding to diagnostic mode will also be generated.
339+
340+
The tar files contains files on the format `<pid of a MDE process>.data`.
341+
The data file can be read using the command:
342+
343+
`perf report -i <pid>.data`
344+
332345
333346
#### Use OS trace (for macOS only)
334347

0 commit comments

Comments
 (0)