Skip to content

Document complete list of fundamental profiling events#722

Open
vagxrth wants to merge 4 commits intoprecice:masterfrom
vagxrth:content/events
Open

Document complete list of fundamental profiling events#722
vagxrth wants to merge 4 commits intoprecice:masterfrom
vagxrth:content/events

Conversation

@vagxrth
Copy link

@vagxrth vagxrth commented Feb 20, 2026

Summary

This updates the Fundamental Events section of the performance analysis docs to include the full set of currently emitted fundamental profiling events.

What changed

  • Updated /content/docs/tooling/tooling-performance-analysis.md
  • Expanded the event list beyond the previously documented subset
  • Added entries for communication, coupling, synchronization, mapping, acceleration, and convergence events
  • Documented dynamic M2N event names as:
    • m2n.requestPrimaryRankConnection.<participant>
    • m2n.acceptPrimaryRankConnection.<participant>
  • Kept user-defined events out of this list (as requested in the issue)

Why

Issue #705 reported that not all fundamental events were explained in the docs page:
/tooling-performance-analysis.html#fundamental-events.

This PR aligns the documentation with the event names currently used in profiling output.

Validation

  • Built locally with:
    • bundle exec jekyll build
  • Checked rendered section locally at:
    • /tooling-performance-analysis.html#fundamental-events

Closes #705

Screenshots

Screenshot 2026-02-20 at 18 01 38 Screenshot 2026-02-20 at 18 01 53

@precice-bot
Copy link
Contributor

This pull request has been mentioned on preCICE Forum on Discourse. There might be relevant details there:

https://precice.discourse.group/t/recent-prs-docs-update-and-ui-fix-for-website/2737/1

@MakisH
Copy link
Member

MakisH commented Feb 22, 2026

Thank you for the PR. We are aware of it and will eventually review it as any other external PR.

Good catch for the typo, we need to check where else we might need to update it.

@vagxrth
Copy link
Author

vagxrth commented Feb 22, 2026

Thank you for the PR. We are aware of it and will eventually review it as any other external PR.

Good catch for the typo, we need to check where else we might need to update it.

Ok got it. Let me know if any other changes are needed.

@MakisH MakisH added the content Content-only issues label Feb 22, 2026
@MakisH MakisH added the GSoC Contributed in the context of the Google Summer of Code label Feb 23, 2026
@MakisH MakisH requested a review from fsimonis February 23, 2026 19:17
@MakisH
Copy link
Member

MakisH commented Feb 23, 2026

@vagxrth is the merging from master automatic? It keeps popping up without any pushes after that.

@vagxrth
Copy link
Author

vagxrth commented Feb 23, 2026

@vagxrth is the merging from master automatic? It keeps popping up without any pushes after that.

I hope it's not an automatic thing but I'll look into it.

Copy link
Member

@fsimonis fsimonis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, thanks for the PR.

There is detail missing here. This information can largely be inferred by the name of the events themselves.

I recommend looking into the code of preCICE to find out what happens inside these events. You can rg --fixed-strings profiling::Fundamental should give you the full list of locations to look at.

* `initialize()` time spent in preCICE `initialize()`. This includes establishing communication between participants, mesh and data transfer, as well as mapping computation.
* `solver.advance` time spent in the solver between `advance()` calls, including the time between `initialize()` and the first `advance()` call.
* `advance()` time spent in preCICE `advance()`. This includes data mapping, data transfer, acceleration.
* `_GLOBAL`: Time spent from the initialization of the events framework to finalization. Starts in participant construction and ends in `finalize` or the destructor.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is deprecated.

Suggested change
* `_GLOBAL`: Time spent from the initialization of the events framework to finalization. Starts in participant construction and ends in `finalize` or the destructor.
* `_GLOBAL` *Deprecated*: Time spent from the initialization of the events framework to finalization. Starts in participant construction and ends in `finalize` or the destructor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content Content-only issues GSoC Contributed in the context of the Google Summer of Code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Not all fundamental events are explained

4 participants