SimGrid (3.28.1) NOT RELEASED YET (v3.29 expected September 22. 2021, 19:21 UTC)
-New features:
- - Non-linear resource sharing: allows to dynamically change the resource
- capacity. Users can change this capacity by setting a callback which will
- be called when SimGrid is sharing the resource between the active
- activities. An activity can be a task running, a read/write IO operation or a
- communication flow.
- - Callback signature: double (double capacity, int n_activities): given the
- current resource's capacity and number of activities running on it,
- returns the new capacity.
- - Note that this callback is in the critical path of the system solve and
- should not take long to execute.
- - Examples:
- - Disk: examples/cpp/io-degradation
- - Link: examples/cpp/network-nonlinear
- - CPU: examples/cpp/exec-cpu-nonlinear
-
-S4u:
- - New: s4u::Disk::set_sharing_policy() and s4u::Host::set_sharing_policy().
- Allows the configuration of non-linear resource sharing for hosts and
- disks.
+New modeling features:
+ - Non-linear resource sharing for decay models:
+ - The total capacity may depend on the number of concurrent usages
+ - For that, resources can take a callback that computes the capacity
+ depending on the idle capacity and the number of concurrent usages
+ - Examples (both cpp and python): io-degradation, network-nonlinear, exec-cpu-nonlinear
+
+ - Dynamic factors for CPU and disk: similarly to dynamic network factors,
+ allows the user to set a callback which can affect the progress of activities
+ (multiplicative factor applied when updating the amount of work remaining).
+ - Example: examples/cpp/exec-cpu-factors
+
+Python:
+ - Added support to programmatic platform creation in Python.
+ Example: examples/python/clusters-multicpu
+
+S4U:
+ - Disk and Host now have a set_sharing_policy() too, for non-linear sharing.
+ This can only be set through the API, not through XML files.
+
+SMPI:
+ - TI Tracing/Replay:
+ - Multiple fixes to ensure reproducibility of tracing
+ - scan/excan can now be replayed
+ - wait action now uses ranks and not pid, as the other ones.
+ - smpi/init and smpi/finalization-barrier are now valid for replays.
+
Documentation:
* New section "Release Notes" documenting recent and current developments.
+ * New section "Modeling I/O: the realistic way" presenting how to properly model disks in SimGrid.
+ * Improvements in API Reference for C++ and Python interfaces.
+ns-3 model:
+ - Make wifi creation compatible with ns-3 version 3.34 too.
+Fixed bugs (FG#.. -> FramaGit bugs; FG!.. -> FG merge requests)
+ (FG: issues on Framagit; GF: issues on GForge; GH: issues on GitHub)
+ - FG#78: Multiple fixes for SMPI replay:
+ - TI tracing of allotallv/w was outputting wrong values
+ - MPI_LOGICAL in fortran is actually 32 bits wide, and not 8.
+ - FG#77: Search feature of doc is broken (update sphinx theme version)
----------------------------------------------------------------------------
SimGrid (3.28) July 14. 2021
versions. Sorry for the inconvenience.
- Dynamic network factors: users can configure a callback to define
the network factors dynamically. This API is available at
- simgrid::kernel::resource::NetworkModelIntf.
+ simgrid::kernel::resource::NetworkModelIntf.
- Users have access to complete information about the current communication
to decide which factor to apply. This includes: message size, source and
- destination hosts, links and zones traversed.
+ destination hosts, links and zones traversed.
- Dynamic factors for both latency and bandwidth.
- For more details, see the example in (examples/cpp/network-factors).
+ - Plugin host_energy: the "watt_off" and "watt_per_state" host properties,
+ deprecated since version 3.24, are no longer supported. Instead, use
+ "wattage_off" and "wattage_per_state".
XBT:
- xbt_assert is not disabled anymore, even when built with enable_debug=off.
