1 /*! \page options Simgrid options and configurations
3 \htmlinclude .options.doc.toc
5 \section options_simgrid_configuration Changing SimGrid's behavior
7 A number of options can be given at runtime to change the default
8 SimGrid behavior. In particular, you can change the default cpu and
11 \subsection options_simgrid_configuration_fullduplex Using Fullduplex
13 Experimental fullduplex support is now available on the svn branch. In order to fullduple to work your platform must have two links for each pair
14 of interconnected hosts, see an example here:
16 simgrid_svn_sources/exemples/msg/gtnets/fullduplex-p.xml
19 Using fullduplex support ongoing and incoming communication flows are
20 treated independently for most models. The exception is the LV08 model which
21 adds 0.05 of usage on the opposite direction for each new created flow. This
22 can be useful to simulate some important TCP phenomena such as ack compression.
24 Running a fullduplex example:
26 cd simgrid_svn_sources/exemples/msg/gtnets
27 ./gtnets fullduplex-p.xml fullduplex-d.xml --cfg=fullduplex:1
30 \subsection options_simgrid_configuration_alternate_network Using alternative flow models
32 The default simgrid network model uses a max-min based approach as
33 explained in the research report
34 <a href="ftp://ftp.ens-lyon.fr/pub/LIP/Rapports/RR/RR2002/RR2002-40.ps.gz">A Network Model for Simulation of Grid Application</a>.
35 Other models have been proposed and implemented since then (see for example
36 <a href="http://mescal.imag.fr/membres/arnaud.legrand/articles/simutools09.pdf">Accuracy Study and Improvement of Network Simulation in the SimGrid Framework</a>)
37 and can be activated at runtime. For example:
39 ./mycode platform.xml deployment.xml --cfg=workstation/model:compound --cfg=network/model:LV08 -cfg=cpu/model:Cas01
42 Possible models for the network are currently "Constant", "CM02",
43 "LegrandVelho", "GTNets", Reno", "Reno2", "Vegas". Others will
44 probably be added in the future and many of the previous ones are
45 experimental and are likely to disappear without notice... To know the
46 list of the currently implemented models, you should use the
47 --help-models command line option.
50 ./masterslave_forwarder ../small_platform.xml deployment_masterslave.xml --help-models
51 Long description of the workstation models accepted by this simulator:
52 CLM03: Default workstation model, using LV08 and CM02 as network and CPU
53 compound: Workstation model allowing you to use other network and CPU models
54 ptask_L07: Workstation model with better parallel task modeling
55 Long description of the CPU models accepted by this simulator:
56 Cas01_fullupdate: CPU classical model time=size/power
57 Cas01: Variation of Cas01_fullupdate with partial invalidation optimization of lmm system. Should produce the same values, only faster
58 CpuTI: Variation of Cas01 with also trace integration. Should produce the same values, only faster if you use availability traces
59 Long description of the network models accepted by this simulator:
60 Constant: Simplistic network model where all communication take a constant time (one second)
61 CM02: Realistic network model with lmm_solve and no correction factors
62 LV08: Realistic network model with lmm_solve and these correction factors: latency*=10.4, bandwidth*=.92, S=8775
63 Reno: Model using lagrange_solve instead of lmm_solve (experts only)
64 Reno2: Model using lagrange_solve instead of lmm_solve (experts only)
65 Vegas: Model using lagrange_solve instead of lmm_solve (experts only)
68 \section options_modelchecking Model-Checking
69 \subsection options_modelchecking_howto How to use it
70 To enable the experimental SimGrid model-checking support the program should
71 be executed with the command line argument
75 Properties are expressed as assertions using the function
77 void MC_assert(int prop);