Commit 24770076 authored by Millian Poquet's avatar Millian Poquet
Browse files

doc: usage trace profile

parent 5cc9008e
......@@ -251,6 +251,8 @@ both the ``from`` and the ``to`` fields.
"to": "nfs"
}
.. _smpi_trace_replay_profile:
SMPI trace replay
^^^^^^^^^^^^^^^^^
Profiles of this type correspond to the replay of a SMPI time-independent trace. Such traces allow to see the fine-grained behavior of MPI applications.
......@@ -283,5 +285,30 @@ Profiles of this type correspond to the replay of a SMPI time-independent trace.
"trace": "smpi/compute_only/traces.txt"
}
Usage trace replay
^^^^^^^^^^^^^^^^^^
Profiles of this type correspond to the replay of usage traces over time.
.. warning::
**This profile requires SimGrid host to have many cores for precision.**
This profile shares the same warnings as :ref:`smpi_trace_replay_profile`.
Each trace file contains a sequence of :math:`(usage, flops)` tuples.
:math:`flops` are executed in sequence on the target host,
using a :math:`usage \in [0,1]` fraction of the host computing load.
The usage replay is based on SimGrid cores on the target host.
For example, if one wants to execute 10 flops with usage=0.1 on a 100-core
host, this will be simulated as a single computation-only parallel task of
size=10, where each executor executes 10 flops.
.. code:: json
{
"type": "usage_trace",
"trace": "usage-trace/from-real-trace/3858728.txt"
}
.. _OAR: https://oar.imag.fr/start
.. _Batsim's initial article: https://hal.archives-ouvertes.fr/hal-01333471
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment