commit b15a49c59378ab3e63ea48f8175ae0b9cea23879
parent 4878b02ab4ea7b9f50251d3d9adba5cd1da7217f
Author: Brendan Gregg <brendan.d.gregg@gmail.com>
Date: Tue, 8 Dec 2015 11:25:58 -0800
update
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/README.md b/README.md
@@ -112,8 +112,8 @@ An advantage of having the folded input file (and why this is separate to flameg
$ grep cpuid out.kern_folded | ./flamegraph.pl > cpuid.svg
```
-Provided Example
-================
+Provided Examples
+=================
### Linux perf\_events
@@ -124,7 +124,7 @@ An example output from Linux "perf script" is included, gzip'd, as example-perf-
You can create this using:
```
-gunzip -c example-perf-stacks.txt.gz | ./stackcollapse-perf.pl --kernel | ./flamegraph.pl --color=java --hash > example-perf.svg
+$ gunzip -c example-perf-stacks.txt.gz | ./stackcollapse-perf.pl --kernel | ./flamegraph.pl --color=java --hash > example-perf.svg
```
This shows my typical workflow: I'll gzip profiles on the target, then copy them to my laptop for analysis. Since I have hundreds of profiles, I leave them gzip'd!