+application, the variable \b smpi/simulate-computation should be set to no.
+
+\note
+ This option just ignores the timings in your simulation; it still executes
+ the computations itself. If you want to stop SMPI from doing that,
+ you should check the SMPI_SAMPLE macros, documented in the section
+ \ref SMPI_adapting_speed.
+
+Solution | Computations actually executed? | Computations simulated ?
+---------------------------------- | ------------------------------- | ------------------------
+--cfg=smpi/simulate-computation:no | Yes | No, never
+--cfg=smpi/cpu-threshold:42 | Yes, in all cases | Only if it lasts more than 42 seconds
+SMPI_SAMPLE() macro | Only once per loop nest (see @ref SMPI_adapting_speed "documentation") | Always
+
+\subsection options_model_smpi_adj_file smpi/comp-adjustment-file: Slow-down or speed-up parts of your code.
+
+This option allows you to pass a file that contains two columns: The first column
+defines the section that will be subject to a speedup; the second column is the speedup.
+
+For instance:
+
+\verbatim
+"start:stop","ratio"
+"exchange_1.f:30:exchange_1.f:130",1.18244559422142
+\endverbatim
+
+The first line is the header - you must include it.
+The following line means that the code between two consecutive MPI calls on
+line 30 in exchange_1.f and line 130 in exchange_1.f should receive a speedup
+of 1.18244559422142. The value for the second column is therefore a speedup, if it is
+larger than 1 and a slow-down if it is smaller than 1. Nothing will be changed if it is
+equal to 1.
+
+Of course, you can set any arbitrary filenames you want (so the start and end don't have to be
+in the same file), but be aware that this mechanism only supports @em consecutive calls!
+
+\note
+ Please note that you must pass the \b -trace-call-location flag to smpicc
+ or smpiff, respectively! This flag activates some macro definitions in our
+ mpi.h / mpi.f files that help with obtaining the call location.