-If the "application" is in fact doing a "live replay" of another MPI
-app (e.g., ScalaTrace's replay tool, various on-line simulators that
-run an app at scale), the computation due to the replay logic should
-not be simulated by SMPI. In that case the \b
-smpi/simulation_computation item can be set to 'no' causing all the
-compute bursts between MPI calls to be ignored by SMPI. Then only the
-communications are simulated. This implies to add explicit calls to \c
-smpi_execute() in the "application" to simulate computations.
+ In some cases, however, one may wish to disable simulation of
+application computation. This is the case when SMPI is used not to
+simulate an MPI applications, but instead an MPI code that performs
+"live replay" of another MPI app (e.g., ScalaTrace's replay tool,
+various on-line simulators that run an app at scale). In this case the
+computation of the replay/simulation logic should not be simulated by
+SMPI. Instead, the replay tool or on-line simulator will issue
+"computation events", which correspond to the actual MPI simulation
+being replayed/simulated. At the moment, these computation events can
+be simulated using SMPI by calling internal smpi_execute*() functions.
+
+To disable the benchmarking/simulation of computation in the simulated
+application, the variable \b
+smpi/simulation_computation should be set to no
+
+\subsection options_model_smpi_bw_factor smpi/bw_factor: Bandwidth factors
+
+The possible throughput of network links is often dependent on the
+message sizes, as protocols may adapt to different message sizes. With
+this option, a series of message sizes and factors are given, helping
+the simulation to be more realistic. For instance, the current
+default value is
+
+\verbatim
+65472:0.940694;15424:0.697866;9376:0.58729;5776:1.08739;3484:0.77493;1426:0.608902;732:0.341987;257:0.338112;0:0.812084
+\endverbatim