-SimGrid (3.30.1) NOT RELEASED YET (v3.31 expected March 20. 2022, 15:33 UTC)
+SimGrid (3.31.1) NOT RELEASED YET (v3.32 expected June 21. 2022, 09:13 UTC)
+
+----------------------------------------------------------------------------
+
+S4U:
+ - kill signal Comm::on_completion that was not working anyway.
+ - Expose signals Activity::on_suspend and Activity::on_resume
+
+SimGrid (3.31) March 22. 2022.
The ненасильство release. We stand against war.
MC:
- Rework the internals, for simpler and modern code. This shall unlock many future improvements.
- - You can now define plugins onto the DFS explorer (previously called SafetyChecker), using the
+ - You can now define plugins onto the DFS explorer (previously called SafetyChecker), using the
declared signals. See CommunicationDeterminism for an example.
- Support mutex, semaphore and barrier in DPOR reduction
- Seems to work on Arm64 architectures too.
- tracing: ensure that we dump the TI traces continuously during execution and
not just at the end, reducing memory cost and performance hit.
- Update OpenMPI collectives selection logic to match current one (4.1.2)
+ - Add a coherence check for collective operation order and root/MPI_Op
+ coherence. Potentially costly so not activated unless smpi:pendantic is set
+ or -analyze is given.
S4U:
- New signal: Engine::on_simulation_start_cb()
- - Introduce a new execution mode with this_actor::thread_execute(). This simulate
+ - Introduce a new execution mode with this_actor::thread_execute(). This simulate
the execution of a certain amount of flops by multiple threads ran by a host. Each
thread executes the same number of flops, given as argument. An example of this new
function can be found in examples/cpp/exec-threads.
- - Reimplementation of barriers natively.
- Previously, they were implemented on top of s4u::Mutex and s4u::ConditionVariable.
+ - Reimplementation of barriers natively.
+ Previously, they were implemented on top of s4u::Mutex and s4u::ConditionVariable.
The new version should be faster (and can be used in the model-checker).
- Actor::get_restart_count(): Returns the number of reboots that this actor did.
- MSG_barrier_destroy now expects a non-const msg_barrier parameter.
New plugin: the Chaos Monkey (killing actors at any time)
- - Along with the new simgrid-monkey script, it tests whether your simulation
- resists resource failures at any possible timestamp in your simulation.
- - It is mostly intended to test the simgrid core in extreme conditions,
+ - Along with the new simgrid-monkey script, it tests whether your simulation
+ resists resource failures at any possible timestamp in your simulation.
+ - It is mostly intended to test the simgrid core in extreme conditions,
but some users may find it interesting too.
Models:
- - New model for parallel task: ptask_BMF.
- - More realistic sharing of heterogeneous resources compared to ptask_L07.
+ - New solver for parallel task: BMF.
+ - More realistic sharing of heterogeneous resources compared to the fair
+ bottleneck solver used by ptask_L07.
- Implement the BMF (Bottleneck max fairness) fairness.
- Improved resource sharing for parallel tasks with sub-flows (parallel
communications between same source and destination inside the ptask).
- Parameters:
- - "--cfg=host/model:ptask_BMF": enable the model.
+ - "--cfg=host/model:ptask_L07 --cfg=host/solver:bmf": enable the ptask
+ model with BMF solver.
- "--cfg=bmf/max-iterations: <N>": maximum number of iterations performed
by BMF solver (default: 1000).
- - "--cfg=bmf/selective-update:<true/false>": enable/disable the
- selective-update optimization. Only invalidates and recomputes modified
- parts of inequations system. May speed up simulation if sparse resource
- utilization (default: false).
+ - "--cfg=bmf/precision: <N>": numerical precision used when computing
+ resource sharing (default: 1e-12).
- This model requires Eigen3 library. Make sure Eigen3 is installed to use BMF.
General:
- FG#101: LGPL 2.1 is deprecated license
- FG#104: "make uninstall" not up-to-date
- GH#151: Missing mutexes for DPOR.
+ - FG#105: "Variable penalty should not be negative!" with in-flight messages and bandwidth profiles
----------------------------------------------------------------------------
