Skip to content

Fix minor issues in tooling/performance-analysis #272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 8, 2023
Merged

Fix minor issues in tooling/performance-analysis #272

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
99a9237
Update tooling-performance-analysis.md
MakisH Jun 2, 2023
2353669
Update tooling-performance-analysis.md
MakisH Aug 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions pages/docs/tooling/tooling-performance-analysis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ The general workflow looks as follows:

1. Run the simulation
2. Merge the event files
3. Analyze each participant, which executes a mapping or computes acceleration
3. Analyze each participant executing a mapping or computing acceleration
4. Analyze each participant to check for load-imbalance between ranks
5. Visualize the simulation to check for load-imbalance between participants

Expand All @@ -120,7 +120,7 @@ An example could look like this:
└── precice-config.xml
```

To find and merge these files run:
where the naming pattern is `participant-rank-file_number`. To find and merge these files run:

```console
$ ls
Expand All @@ -144,9 +144,9 @@ events.json
```

The merge command searches passed directories for the event files.
You can also pass individual files if you are not interested in all ranks
You can also pass individual files if you are not interested in all ranks.

The merge command is written in pure python without external dependencies to make it easy to use on clusters.
The merge command is written in pure Python, without external dependencies, to make it easy to use on clusters.
After you run `precice-events merge`, you end up with a single file, which can be additionally compressed and transferred to another machine.
This is especially handy for very large and/or long simulations on clusters or supercomputers.

Expand Down Expand Up @@ -186,7 +186,7 @@ Writing to trace.json
An example trace visualization using `ui.perfetto.dev` of the [elastic tube 1d tutorial](tutorials-elastic-tube-1d.html) looks as follows.
Note the alternating executions of the solver due to the serial coupling scheme.

![example of the elastic tube 1d tutorial visualized by perfetto](images/docs/tooling/profiling-aste-perfetto-serial.png)
![example of the elastic tube 1d tutorial visualized by perfetto](images/docs/tooling/profiling-elastictube1d-serial.png)

An example trace visualization using `ui.perfetto.dev` of a parallel [ASTE](tooling-aste.html) run on two and four ranks looks as follows.
This first version contains only fundamental events, which is the default profiling setting.
Expand Down