X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/ca8a39f9679abcef3c5c546966e5144ec41f67c3..5e6d17f5b101a50b23264f99ecb7c74383a4823f:/ChangeLog diff --git a/ChangeLog b/ChangeLog index 2630539095..153d3171da 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,71 @@ +SimGrid (3.3.4) unstable; urgency=low + + The "Desktop Grid needs love too" release. + + Models improvements: + * Major speedup in the maxmin system solving by using lazy evaluation + Instead of solving completely the maxmin system at each iteration, + only invalidate (and recompute) the modified parts. + This new feature is enabled in default models but you can try to + turn it on with "--cfg:maxmin-selective-update=1" for other models. + * Cas01 IMproved as default CPU model + This CPU model is the same Cas01 model, but it uses the + maxmin-selective-update flag and a heap structure to manage + actions on SURF kernel. + It reduces the complexity to find the next action to finish and, + consequently, it's faster than the old Cas01. + This is the new default CPU model (Cas01). + * Rename the old Cas01 model to Cas01_fullupdate + Keep the old cpu model Cas01 with the new name of Cas01_fullupdate. + Use "--cfg=cpu_model:Cas01_fullupdate" to use the old default CPU model. + * CpuTI (CPU Trace Integration) + A new CPU model whose objective is simulate faster when using + availability trace files. + Instead of using a full featured, over engineered maxmin system for + CPU modeling, this model does the pre-integration of traces files + to calculate the amount of CPU power available, and so, executes + faster than the old CPU models. + Use "--cfg=cpu_model:CpuTI" to change to this CPU model. + * Use LV08 as default network model since it gives better accuracy + for small messages and shouldn't change things for big ones. + Use --cfg=network_model:CM02 to get the previous behavior. + + + ****************************************** + *DO NOT MIX 3.3.4 RESULTS WITH OLDER ONES* + ****************************************** + * The new CPU model may changes simulations! + The point is that events occurring at the exact same timestamp + are not scheduled in the same order with the old and new + version. This may be enough to completely change the execution + of simulations in some cases. + * The new network model will change simulations! + This new model is more realistic than the previous one, so you + should consider redoing your old experiments with this model. + Sorry for the inconvenience. + + MSG: + * Port of MSG's mailbox on top of SIMIX network + The put/get mechanism was greatly simplified thanks to the new SIMIX module. + + SIMIX: + * New SIMIX network module + It provides a rendez-vous point (aka mailbox) based send/recv API to perform + synchronous communication. + + Bug fixes: + * GTNetS wrappers should now be usable again (and betterly tested too) + * Fix a major regression from 3.2 where the timeout provided to + MSG_task_put_with_timeout() was used as absolute time before which + the comm should be done. + * Fix a source-level compatibility glitch from 3.2: after defining + MSG_USE_DEPRECATED, you can use the old name + MSG_task_put_with_time_out() for MSG_task_put_with_timeout() + * Allow to compile from the SVN with automake 1.11 + * Fix some problems when using the "start_time" tag in deployment XMLs. + + -- Da SimGrid team + SimGrid (3.3.3) stable; urgency=low The "Need for Speed" release. @@ -14,15 +82,16 @@ SimGrid (3.3.3) stable; urgency=low Here are some approximate speedup measurements (on master/slaves simulations lasting between 10s and 20s each): - 3.3.1 -> 3.3.2: -15% - 3.3.2 -> 3.3.3: +40% - 3.3.1 -> 3.3.3: +40% - 3.3.1 with inline patch -> 3.3.3: +30% + 3.3.1 -> 3.3.2: about same performance + 3.3.2 -> 3.3.3: 40% speedup + 3.3.1 -> 3.3.3: 40% speedup + 3.3.1 with inline patch -> 3.3.3: 30% speedup Our reading is that the refactoring which occurred in 3.3.2 made us suffer much more from the xbt_dynar_foreach low performance, but once we solved this, this refactoring proved to be very performance - effective. + effective. From the 40% speedup, somehow, 10% are due to the + inlining and 30% to the refactoring. That's a pitty that gcc cannot inline functions placed in other files alone. We have to choose between: @@ -31,7 +100,7 @@ SimGrid (3.3.3) stable; urgency=low - live with low performance - switch to a decent compiler such as icc (not quite possible). - -- Da SimGrid team + -- Da SimGrid team Thu, 20 Aug 2009 21:21:33 +0200 SimGrid (3.3.2) stable; urgency=low