X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/94b9b9a993d99cd83f8299227ed6e89bca99924f..a984f41a503299f5d2e660422520a7d0e0e5391d:/ChangeLog diff --git a/ChangeLog b/ChangeLog index 909594f089..a563d4078e 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,6 +1,105 @@ ---------------------------------------------------------------------------- -SimGrid (3.27.1) NOT RELEASED YET (v3.28 expected June 21. 2021, 03:32 UTC) +SimGrid (3.29.1) NOT RELEASED YET (v3.30 expected December 21. 2021, 15:59 UTC) + +S4U: + - New function: Engine::run_until(date), to split the simulation. + - New signal: Activity::on_veto, to detect when an activity fails to start. + - New function: Engine::track_vetoed_activities() to interrupt run() + when an activity fails to start, and to keep track of such activities. + Please see the corresponding example for more info. + +SMPI: + - Dynamic costs for MPI operations: New API to allow users to dynamically + change injected costs for MPI_Recv, MPI_Send and MPI_Isend operations. + Alternative for smpi/or, smpi/os and smpi/ois configuration options. + +Documentation: + - New section: "SimGrid MPI calibration of a Grid5000 cluster" + presenting how to properly calibrate MPI communications in SimGrid. + - Complete and reword the platform section, which is now completed. + +Python: + - Thread contexts are used by default with Python bindings. Other kinds of + contexts revealed unstable, specially starting with pybind11 v2.8.0. + +---------------------------------------------------------------------------- + +SimGrid (3.29) October 7. 2021 + +The "Ask a stupid question" release. + +We wish that every user ask one question about SimGrid to celebrate. +On Mattermost, Stack Overflow or using the issues tracker. + + +New modeling features: + - Non-linear resource sharing, modeling resources whose performance heavily degrades with contention: + - The total capacity may be updated dynamically through a callback + and depends mainly on the number of concurrent flows. + - Examples (both cpp and python): io-degradation, network-nonlinear, exec-cpu-nonlinear + + - Dynamic factors: model variability in the speed of activities + - Each action can now have a factor that affects its progression. + This multiplicative factor is applied when updating the amount of work + remaining, thereby an activity with factor=0.5 only uses half of the + instantaneous power/bandwidth it is allocated and will appear twice + slower than what it actually consumes. + - This can be used to model a overhead (e.g., there is a 20 bytes + header in a 480 bytes TCP packet so the factor 0.9583) but the novelty + is this factor can now easily be adjusted depending on activity's and + resources characteristics. + - This existed for network (e.g., the effective bandwidth depends + on the message in SMPI piecewise-linear network model) but it is now + more general (the factor may depend on the source and destination and + thus account to different behaviors for intra-node communications and + extra-node communications) and is available for CPUs (e.g., if you + want to model an affinity as in the "Unrelated Machines" problem in + scheduling) and disks (e.g., if you want to model a stochastic + capacity) too. + - For that, resources can be provided with a callback that computes + the activity factor when creating the action. + - Example: examples/cpp/exec-cpu-factors + - The same mechanism is also available for the latency, which + allows to easily introduce complex variability patterns. + +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. + - exit() is now intercepted by SMPI to avoid premature shutdown of + simulation. First non 0 return codes is returned as simulation return + code. + +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 + +The Victoriadagarna Release. New features: - C++ platform interface: Users can now describe their platform directly in C++. @@ -27,6 +126,7 @@ S4U: parameter by reference, instead of a pointer. - Fixed a bug where Activity::wait_for() killed the activity on timeout. Explicitly cancel the activity to get back to previous behavior. + - New: Link::set_concurrency_limit() to limit the amount of concurrent flows. SMPI: - The default SMPI compiler flags are no more taken from the environment. @@ -83,6 +183,17 @@ Models: This change may impact on the timing of your simulation results. Take care when comparing simulations from different SimGrid's 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. + - 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. + - 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. @@ -90,6 +201,9 @@ XBT: Documentation: - New tutorial: Model-checking and formal assessment - New sections: "Demystifying the routing" and "C++ platforms" + - Update and improve the part on visualization in MPI and Algo tutorials. + - Improve the section on routing: how to define it, how it's used internally + - Fix many issues, broken links and missing references in doxygen and Sphinx LUA: - Lua platform files are deprecated. Their support will be dropped after v3.31.