Skip to main content

preCICE profiling tools

Workflow

  1. Optional Enable <profiling mode="all"/> in the preCICE configuration of your case to get the profiling information.
  2. Run the preCICE simulation.
  3. Run precice-profiling-merge to combine all emitted profiling files of the simulation into a single profiling.db file.
  4. Analyze the solvers:
    • Use precice-profiling-analyze to get a breakdown of an individual solver.
    • Use precice-profiling-trace to visualize the data.
    • Use precice-profiling-export to export the data as CSV to import in other software.

Tools

merge

Merges profiling files emitted by each rank of each participant into a single easily portable file. Creates a profiling.db by default.

export

Transforms all events to a tabular format and exports the result as a CSV format. The columns Participant, and Rank can be used to filter the dataset to extract individual participants or specific ranks.

Reads profiling.db and creates profiling.csv by default.

trace

Transforms all events to the Google Trace Format which can be visualized by tools such as about::tracing in Chromium based browsers or perfetto.dev.

Reads profiling.db and creates trace.json by default.

analyze

Analyzes a given solver and returns a table of all timings including some statistics based on their duration.

Reads profiling.db by default.

HPC users

HPC users or users of locked down clusters without easy access to pip can download the merge command as a standalone file and run it without installing additional dependencies.

wget -O precice-profiling-merge https://raw.githubusercontent.com/precice/profiling/refs/heads/main/preciceprofiling/merge.py
chmod +x precice-profiling-merge

Licensing

This repository contains modified part of the the precice-profiling script, which is part of the preCICE library (precice/precice tools/profiling/precice-profiling) and licensed under the LGPv3 license. The two copyright holders David Schneider (@davidscn david.schneider@ipvs.uni-stuttgart.de) and Frédéric Simonis (@fsimonis frederic.simonis@ipvs.uni-stuttgart.de) decided on 23. June 2025 15:00 CET to rerelease the content of the precice-profiling script in this repository under the MIT license.

Release files for precice-profiling 2.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for precice-profiling 2.1.0
File Size Uploaded
precice_profiling-2.1.0.tar.gz 16.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for precice-profiling 2.1.0
File Interpreter ABI Platform
precice_profiling-2.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 35.4 kB

Release files / precice_profiling-2.1.0.tar.gz

Download URL precice_profiling-2.1.0.tar.gz
Size 16.4 kB
Tags Source
SHA-256 checksum
How to use checksums
98274a9f7d60264ca54368f0eb6147a6ba522be4c03e12ba16f1abe9c5f2d2d2
BLAKE2b-256 checksum
How to use checksums
0a7be9c4d35d43f59aa79400271111ce21d7f29d1b41a909eb1bd60d6a578d2d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 9, 2025.

Transparency log

Release files / precice_profiling-2.1.0-py3-none-any.whl

Download URL precice_profiling-2.1.0-py3-none-any.whl
Size 19.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ca25ba8d7312e087f85ba590dc33882736b9a873900a33f29139e23ddda4cc98
BLAKE2b-256 checksum
How to use checksums
8d4930a0861e35ae46b7275af9688c706bb13a582a3fee276d26a966e584a855
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 9, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

2.1.0 This release

2 release files

2.0.4

2 release files

2.0.3

2 release files

2.0.2

2 release files

2.0.1

2 release files

2.0.0

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page