- \b storage/model: specify the used storage model (there is currently only one such model - this option is hence only useful for future releases)
- \b vm/model: specify the model for virtual machines (there is currently only one such model - this option is hence only useful for future releases)
-%As of writing, the following network models are accepted. Over
+As of writing, the following network models are accepted. Over
the time new models can be added, and some experimental models can be
removed; check the values on your simulators for an uptodate
information. Note that the CM02 model is described in the research report
The network and CPU models that are based on lmm_solve (that
is, all our analytical models) accept specific optimization
configurations.
- - items \b network/optim and \b CPU/optim (both default to 'Lazy'):
+ - items \b network/optim and \b cpu/optim (both default to 'Lazy'):
- \b Lazy: Lazy action management (partial invalidation in lmm +
heap in action remaining).
- \b TI: Trace integration. Highly optimized mode when using
\subsubsection options_model_network_crosstraffic Simulating cross-traffic
-%As of SimGrid v3.7, cross-traffic effects can be taken into account in
+As of SimGrid v3.7, cross-traffic effects can be taken into account in
analytical simulations. It means that ongoing and incoming
communication flows are treated independently. In addition, the LV08
model adds 0.05 of usage on the opposite direction for each new
Note that with the default host model this option is activated by default.
-\subsubsection options_model_network_coord Coordinated-based network models
-
-When you want to use network coordinates, as it happens when you use
-an \<AS\> in your platform file with \c Vivaldi as a routing (see also
-Section \ref pf_routing_model_vivaldi "Vivaldi Routing Model"), you must
-set the \b network/coordinates to \c yes so that all mandatory
-initialization are done in the simulator.
-
\subsubsection options_model_network_sendergap Simulating sender gap
(this configuration item is experimental and may change or disapear)
5+11*1
\endverbatim
-%As 5 is the startup cost and 1 is the cost per byte.
+As 5 is the startup cost and 1 is the cost per byte.
\note
The order of sections can be arbitrary; they will be ordered internally.
Internally, in order to speed up execution, we use a counter to keep track
on how often we already checked if the handle is now valid or not. Hence, we
actually use counter*SLEEP_TIME, that is, the time MPI_Test() causes the process
- to sleep increases linearly with the number of previously failed testk.
+ to sleep increases linearly with the number of previously failed tests. This
+ behavior can be disabled by setting smpi/grow-injected-times to no. This will
+ also disable this behavior for MPI_Iprobe.
\subsection options_model_smpi_use_shared_malloc smpi/use-shared-malloc: Factorize malloc()s
- \c model-check/visited: \ref options_modelchecking_visited
- \c network/bandwidth-factor: \ref options_model_network_coefs
-- \c network/coordinates: \ref options_model_network_coord
- \c network/crosstraffic: \ref options_model_network_crosstraffic
- \c network/latency-factor: \ref options_model_network_coefs
- \c network/maxmin-selective-update: \ref options_model_optim
- \c smpi/comp-adjustment-file: \ref options_model_smpi_adj_file
- \c smpi/cpu-threshold: \ref options_smpi_bench
- \c smpi/display-timing: \ref options_smpi_timing
+- \c smpi/grow-injected-times: \ref options_model_smpi_test
- \c smpi/host-speed: \ref options_smpi_bench
- \c smpi/IB-penalty-factors: \ref options_model_network_coefs
- \c smpi/iprobe: \ref options_model_smpi_iprobe
