s/ *$// over all RST files (no content modification)

[simgrid.git] / docs / source / Modeling_howtos.rst

.. raw:: html

   <object id="TOC" data="graphical-toc.svg" type="image/svg+xml"></object>
   <script>
   window.onload=function() { // Wait for the SVG to be loaded before changing it
     var elem=document.querySelector("#TOC").contentDocument.getElementById("PlatformBox")
     elem.style="opacity:0.93999999;fill:#ff0000;fill-opacity:0.1;stroke:#000000;stroke-width:0.35277778;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1";
   }
   </script>
   <br/>
   <br/>

.. _howto:

Modeling Hints
##############

There is no perfect model. Only models that are adapted to the
specific study that you want to do. SimGrid provides several advanced
mechanisms that you can adapt to model the situation that you are
interested in, and it is often uneasy to see where to start with.
This page collects several hints and tricks on modeling situations.
Even if you are looking for a very advanced, specific use case, these
examples may help you to design the solution you need.

.. _howto_science:

Doing Science with SimGrid
**************************

Many users are using SimGrid as a scientific instrument for their
research. This tool was indeed invented to that extent, and we strive
to streamline this kind of usage. But SimGrid is no magical tool, and
it is of your responsibility that the tool actually provides sensible
results. Fortunately, there is a vast literature on how to avoid
Modeling & Simulations pitfalls. We review here some specific works.

In `An Integrated Approach to Evaluating Simulation Credibility
<http://www.dtic.mil/dtic/tr/fulltext/u2/a405051.pdf>`_, the authors
provide a methodology enabling the users to increase their confidence
in the simulation tools they use. First of all, you must know what you
actually expect to discover whether the tool actually covers your
needs. Then, as they say, "a fool with a tool is still a fool", so you
need to think about your methodology before you submit your articles.
`Towards a Credibility Assessment of Models and Simulations
<https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20080015742.pdf>`_
gives a formal methodology to assess the credibility of your
simulation results.

`Seven Pitfalls in Modeling and Simulation Research
<https://dl.acm.org/citation.cfm?id=2430188>`_ is even more
specific. Here are the listed pitfalls: (1) Don't know whether it's
modeling or simulation, (2) No separation of concerns, (3) No clear
scientific question, (4) Implementing everything from scratch, (5)
Unsupported claims, (6) Toy duck approach, and (7) The tunnel view. As
you can see, this article is a must read. It's a pity that it's not
freely available, though.

.. _howto_churn:

Modeling churn (e.g., in P2P)
*****************************

One of the biggest challenges in P2P settings is to cope with the
churn, meaning that resources keep appearing and disappearing. In
SimGrid, you can always change the state of each host manually, with
eg :cpp:func:`simgrid::s4u::Host::turn_on`. To reduce the burden when
the churn is high, you can also attach a **state profile** to the host
directly.

This can be done through the XML file, using the ``state_file``
attribute of :ref:`pf_tag_host`, :ref:`pf_tag_cluster` or
:ref:`pf_tag_link`. Every line (but the last) of such files describes
timed events with the form "date value". Example:

.. code-block:: python

   1 0
   2 1
   LOOPAFTER 8

This file uses a cryptic yet simple formalism:

  * At time t = 1, the host is turned off (a zero value means OFF).
  * At time t = 2, the host is turned back on (any other value than zero means ON).
  * At time t = 10, the profile is reset (as we are 8 seconds after the last event). Then the host will be turned off again at time t = 11.

If your profile does not contain any LOOPAFTER line, then it will be executed only once and not in a repetitive way.

Another possibility is to use the
:cpp:func:`simgrid::s4u::Host::set_state_profile()` or
:cpp:func:`simgrid::s4u::Link::set_state_profile()` functions. These
functions take a profile, that can be a fixed profile exhaustively
listing the events, or something else if you wish.

For further reading, you could turn to :ref:`this example <s4u_ex_comm_failure>`
on how to react to communication failures, or  :ref:`this one <s4u_ex_platform_state_profile>`
on how to attach a state profile to hosts and react to execution failures.

.. _howto_multicore:

Modeling multicore machines
***************************

Default model
=============

Multicore machines are very complex, and there are many ways to model
them. The default models of SimGrid are coarse grain and capture some
elements of this reality. Here is how to declare simple multicore hosts:

.. code-block:: xml

   <host id="mymachine" speed="8Gf" core="4"/>

It declares a 4-core host called "mymachine", each core computing 8
GFlops per second. If you put one activity of 8 GFlops on this host, it
will be computed in 1 second (by default, activities are
single-threaded and cannot leverage the computing power of more than
one core). If you run two such activities simultaneously, they will still be
computed in one second, and so on up to 4 activities. If you start 5 activities,
they will share the total computing power, and each activity will be
computed in 5/4 = 1.25 seconds. This is a very simple model, but that is
all what you get by default from SimGrid.

Pinning tasks to cores
======================

The default model does not account for task pinning, where you
manually select on which core each of the existing activity should
execute. The best solution to model this is probably to model your
4-core processor as 4 distinct hosts, and assigning the activities to
cores by migrating them to the declared hosts. In some sense, this
takes the whole Network-On-Chip idea really seriously.

Some extra complications may arise here. If you have more activities than
cores, you'll have to `schedule your activities
<https://en.wikipedia.org/wiki/Scheduling_%28computing%29#Operating_system_process_scheduler_implementations)>`_
yourself on the cores (so you'd better avoid this complexity). Since
you cannot have more than one network model in a given SimGrid
simulation, you will end up with a TCP connection between your cores. A
possible work around is to never start any simulated communication
between the cores and have the same routes from each core to the
rest of the external network.

Modeling a multicore CPU as a set of SimGrid hosts may seem strange
and unconvincing, but some users achieved very realistic simulations
of multicore and GPU machines this way.

Modeling machine boot and shutdown periods
******************************************

When a physical host boots up, a lot of things happen. It takes time
during which the machine is not usable but dissipates energy, and
programs actually die and restart during a reboot. Since there are many
ways to model it, SimGrid does not do any modeling choice for you but
the most obvious ones.

Any actor running on a host that is shut down will be killed and all
its activities will be automatically canceled. If the actor killed was
marked as auto-restartable (with :cpp:func:`simgrid::s4u::Actor::set_auto_restart`),
it will start anew with the same parameters when the host boots back up.

By default, shutdowns and boots are instantaneous. If you want to
add an extra delay, you have to do that yourself, for example from a
`controller` actor that runs on another host. The best way to do so is
to declare a fictional pstate where the CPU delivers 0 flop per
second (so every activity on that host will be frozen when the host is
in this pstate). When you want to switch the host off, your controller
switches the host to that specific pstate (with
:cpp:func:`simgrid::s4u::Host::set_pstate`), waits for the amount of
time that you decided necessary for your host to shut down, and turns
the host off (with :cpp:func:`simgrid::s4u::Host::turn_off`). To boot
up, switch the host on, go into the specific pstate, wait a while and
go to a more regular pstate.

To model the energy dissipation, you need to put the right energy
consumption in your startup/shutdown specific pstate. Remember that
the energy consumed is equal to the instantaneous consumption
multiplied by the time in which the host keeps in that state. Do the
maths, and set the right instantaneous consumption to your pstate, and
you'll get the whole boot period to consume the amount of energy that
you want. You may want to have one fictional pstate for the boot
period and another one for the shutdown period.

Of course, this is only one possible way to model these things. YMMV ;)

.. _howto_parallel_links:

Modeling parallel links
***********************

Most HPC topologies, such as fat-trees, allow parallel links (a
router A and a router B can be connected by more than one link).
You might be tempted to model this configuration as follows :

.. code-block:: xml

    <router id="routerA"/>
    <router id="routerB"/>

    <link id="link1" bandwidth="10GBps" latency="2us"/>
    <link id="link2" bandwidth="10GBps" latency="2us"/>

    <route src="routerA" dst="routerB">
        <link_ctn id="link1"/>
    </route>
    <route src="routerA" dst="routerB">
        <link_ctn id="link2"/>
    </route>

But that will not work, since SimGrid doesn't allow several routes for
a single `{src ; dst}` pair. Instead, what you should do is:

  - Use a single route with both links (so both will be traversed
    each time a message is exchanged between router A and B)

  - Double the bandwidth of one link, to model the total bandwidth of
    both links used in parallel. This will make sure no combined
    communications between router A and B use more than the bandwidth
    of two links

  - Assign the other link a `FATPIPE` sharing policy, which will allow
    several communications to use the full bandwidth of this link without
    having to share it. This will model the fact that individual
    communications can use at most this link's bandwidth

  - Set the latency of one of the links to 0, so that latency is only
    accounted for once (since both link are traversed by each message)

So the final platform for our example becomes :

.. code-block:: xml

    <router id="routerA"/>
    <router id="routerB"/>

    <!-- This link limits the total bandwidth of all parallel communications -->
    <link id="link1" bandwidth="20GBps" latency="2us"/>

    <!-- This link only limits the bandwidth of individual communications -->
    <link id="link2" bandwidth="10GBps" latency="0us" sharing_policy="FATPIPE"/>

    <!-- Each message traverses both links -->
    <route src="routerA" dst="routerB">
        <link_ctn id="link1"/>
        <link_ctn id="link2"/>
    </route>