Document complete list of fundamental profiling events

[vagxrth]

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

[precice-bot]

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]

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]

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]

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

[vagxrth]

@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.

[fsimonis]

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.

[hanzalahwaheed]

@vagxrth
rather than using git pull, we can try to use git pull --rebase to keep the commit history clean and get rid of cluttered Merge commits. I strongly feel this is valuable to a project in the long run.

[vagxrth]

Screenshots

[precice-bot]

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

https://precice.discourse.group/t/gsoc-2026-introduction-hanzalah-waheed/2745/5

[vagxrth]

@fsimonis resolved all the requested changes in the latest commit.

Screenshots