Skip to content

Commit 0b2c9aa

Browse files
committed
fix typo
1 parent f3eb1f8 commit 0b2c9aa

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@ We provide a basic repro for you to quickly get started with MegaScan.
169169
2. After training, you will find separated trace files in the current directory. The trace files are named as `benchmark-data-{}-pipeline-{}-tensor-{}.json`, where `{}` is the rank number. Now we should aggregate the trace files into a single trace file:
170170

171171
```bash
172-
python scripts/aggregate.py --benchmark . --output benchmark.json
172+
python scripts/aggregate.py --bench-dir . --output benchmark.json
173173
```
174174

175175
3. You can visualize the trace file using Chrome Tracing (or Perfetto UI). Open the trace file in Chrome Tracing by navigating to `chrome://tracing` in your browser (or https://ui.perfetto.dev/). Now you can explore the trace data, zoom in on specific events, and analyze the performance characteristics of your distributed training run.
@@ -191,7 +191,7 @@ python scripts/aggregate.py --benchmark . --output benchmark.json
191191

192192
```bash
193193
python scripts/aggregate.py \
194-
-b . \ # Equivalent to --benchmark
194+
-b . \ # Equivalent to --bench-dir
195195
-d # Enable the detection algorithm, Equivalent to --detect
196196
```
197197
We can see some output that indicated that the GPU 0 may be abnormal:

0 commit comments

Comments
 (0)