Version 3.14 (Dec 25. 2016)
---------------------------
-This version (aka, the Christmas Pi) mainly introduces internal reorganization on the way to the future SimGrid 4 version.
-These changes should be transparent to the users of the MSG, SMPI and SimDag interfaces, even if some buggy features were reworked
+This version (aka, the Christmas Pi) mainly introduces internal reorganization on the way to the future SimGrid 4 version.
+These changes should be transparent to the users of the MSG, SMPI and SimDag interfaces, even if some buggy features were reworked
while some new features were added.
Users are expected to switch to this new version at their own pace, as we do not have the manpower to do any bugfixing on the old releases.
Tom to run a simulation of HPL involving 10^6 processes... Wow. The dlopen privatization schema should even allows to run your ranks
in parallel (even if it's not well tested yet).
-On the Cloud side, we implemented multi-core VMs, which naturally acts as containers of processes;
+On the Cloud side, we implemented multi-core VMs, which naturally acts as containers of processes;
S4U, the future interface of SimGrid 4.0 also progressed quite a bit.
The Storage is currently cleaned up by Fred, and some API changes are to be expected. We are sorry but the exisiting API is so crappy that
Version 3.18 (Dec. 24 2017)
---------------------------
-This is an important version for SimGrid: MSG is now deprecated, and new projects should use S4U instead.
+This is an important version for SimGrid: MSG is now deprecated, and new projects should use S4U instead.
There is still some work to do before SimGrid 4: S4U is not ready for SimDag users yet unfortunately. This will come for sure.
Main changes in the "Ho Ho Ho! SimGrid 4 beta is coming to town" release:
* Convert almost all interesting MSG examples to S4U.
* New model: energy consumption due to the network.
* Major cleanups in the disk and storage subsystems.
- * (+ further deprecate XBT, bug fixes and doc improvement)
+ * (+ further deprecate XBT, bug fixes and doc improvement)
SimGrid 4 *may* be there by the next solstice.
Version 3.19.1 (March 22. 2018)
-------------------------------
-As you may know, we are currently refactoring SimGrid in deep.
+As you may know, we are currently refactoring SimGrid in deep.
Upcoming SimGrid4 will be really different from SimGrid3: modular, standard and extensible vs. layered, homegrown and rigid. C++ vs. C.
Our goal is to smooth this transition, with backward compatibility and automatic update paths, while still progressing toward SimGrid4.
is not finished, but it's not worse than the old one either) while Augustin completed the tutorial for MPI applications. Augustin also
added several non-blocking collectives to SMPI, even if Martin finally decided to release right before he could complete the last ones
(sorry). We continued cutting on XBT, replacing many functions and modules by their standard counterparts in C++11 or in Boost. We are
-now using Catch2 for our unit testing. These cleanups may speedup your simulations by something like 10%.
+now using Catch2 for our unit testing. These cleanups may speedup your simulations by something like 10%.
Version 3.23 (June 25. 2019)
----------------------------
Version 3.27 (March 29. 2021)
-----------------------------
-To celebrate the 1176th anniversary of the siege of Paris by Vikings in 845, we just released another version of SimGrid, the Ragnar Release.
+To celebrate the 1176th anniversary of the siege of Paris by Vikings in 845, we just released another version of SimGrid, the Ragnar Release.
Yeah, that's a stupid release name, but we already had 4 "spring release" in the past, so we needed another name.
* SMPI: can now report leaks and hint about the mallocs and kernels hindering simulation scalability
And the third front is about modernizing the model checker implementation. The current state is very difficult to work with, and we hope that once it's
simplified, we will be able to implement more efficient state space reduction techniques, and also allow more synchronization mechanism to be used in the
-model checker (for now, our dpor algorithm cannot cope with mutexes).
+model checker (for now, our dpor algorithm cannot cope with mutexes).
In parallel to these refactoring, the work on SMPI stability and robustness peacefully continued. The list of MPI applications that can now work with
absolutely no change on top of SMPI really gets impressive... Check it yourself: https://framagit.org/simgrid/SMPI-proxy-apps
* SMPI: improve error handling for incorrect advanced usages.
* Many internal cleanups and refactoring to prepare the future.
-As usual, even the full changelog is only the tip of the iceberg, given the amount of changes in the backstage.
+As usual, even the full changelog is only the tip of the iceberg, given the amount of changes in the backstage.
This release is the big one for the programmatic platform descriptions, that are now fully usable from C++. XML will not
disappear anytime soon, but it is unlikely that we continue developing it in the future. When starting a new project, you should
to fight the technical debt and ensure that you'll still enjoy SimGrid in a decade. Along the same line, we removed the symbols that were
deprecated since 3 releases, as usual.
-Version 3.29 (not released yet)
--------------------------------
+Version 3.29 (October 7. 2021)
+------------------------------
+
+To celebrate the "Ask a stupid question" release, we wish that every user ask one question about SimGrid.
+On `Mattermost <https://framateam.org/simgrid/channels/town-square>`_,
+`Stack Overflow <https://stackoverflow.com/questions/tagged/simgrid>`_,
+or using the `issues tracker <https://framagit.org/simgrid/simgrid/-/issues>`_.
+
+ * Python bindings for the platform creation API
+ * Introduce non-linear resource sharing, allowing decay models
+ * New documentation section on realistic I/O modeling
+ * (+ many bug fixes and internal refactoring)
+
+This release finishes the work on programmatic platforms, that was ongoing since 3.27. It is now possible to define a complete platform in either C++
+or python, and the XML approach is now deprecated. It will probably remain around for a long time, but no evolution is planned. New features will not
+be ported to the XML parser (unless you provide a patch, of course).
+
+This release also paves the way for new models, with the introduction of two new features to the model solver:
+
+ * Non-linear resource sharing was introduced, allowing to model resource whose performance heavily degrades with contention. This may be used in the
+ future for Wi-Fi links, where the total amount of data exchanged in a cell drops when the amount of stations reaches a threshold.
+ * Dynamic factors model variability in the speed of activities. This can be used to model an 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.
+
+ The same mechanism is also available for the latency, which allows to easily introduce complex variability patterns.
+
+These new features are not used yet in the provided models, but this will probably change in future releases.
+
+Version 3.30 (January 30. 2022)
+---------------------------
+
+The Sunday Bloody Sunday release.
+
+In may 2016, the future organization of the S4U activities was drafted on a Hawaiian whiteboard. We defined the life cycle of activities, their types,
+and the way to combine them. All of this had been implemented since, but one piece was still missing: the capacity to express dependencies and vetoes
+that can prevent an activity to start. The underlying idea was to be able to manage application DAGs, a la SimDag, through the S4U API, and have
+maestro to handle the execution of such DAGs.
+
+This release finishes this work, which is presented in a new set of examples (`examples/cpp/dag-*`). The direct consequences on the code base of this
+new feature are:
+
+ * The SimDag API for the simulation of the scheduling of Directed Acyclic Graphs has been finally dropped. It was marked as deprecated for a couple
+ of years.
+ * The removal of SimDag led us to also remove the export to Jedule files that was tightly coupled to SimDag. The instrumentation of DAG simulation
+ is still possible through the regular instrumentation API based on the Paje format.
+
+On the bindings front, we dropped the Lua bindings to create new platforms, as the C++ and Python interfaces are much better to that extend.
+Also, the algorithm tutorial can now be taken in Python, for those of you alergic to C++.
-Release target: September 22. 2021
+Finally, on the SMPI front, we introduced a new documentation section on calibrating the SMPI models from your measurements and fixed some issues
+with the replay mechanism.
