[Simgrid-user] Excessive Memory Use
christopho128 at gmail.com
Mon Jul 25 15:07:01 CEST 2011
The last git version (commit a48d223f) should fix your issues.
The trash of old processes is now cleaned during the simulation (as it
should be), by calling SIMIX_process_empty_trash() automatically after
each time step and not only at the end of the simulation. Sorry about
For MSG_task_cancel(), we guess you have an exception because you may
have called it with a task that was not running (i.e. not started yet
or already finished). But this was a little bit restrictive, and we
have just changed this behavior. Now, MSG_task_cancel() can be called
with a non-running task and nothing happens: the function just returns
I hope it helps.
2011/7/24 Wagner Kolberg <wkolberg at inf.ufrgs.br>:
>> Thanks for using SimGrid. Propeling actual science is the whole
>> purpose of our work, which you prove useful. That's great.
> And thank you for providing it! ;)
>> For SIMIX_process_empty_trash(), I'll fix it in the git tomorrow. I'll
>> also try to see if I can understand why task_cancel was raising the
>> impossible exception. This exception is a bug marker that you
>> shouldn't swallow in your code. I'd appreciate if you could report the
>> next time that you're getting it so that we can fix it. I may come
>> back to you at some point to check my fix for task_cancel.
> Absolutely, I'll keep you posted. And you can contact me directly
> through my e-mail if you want. I'm glad to help in any way I can.
>> As for non blocking communications, it's clear that spawning a new
>> process is quite a lot of work for the simulator where running an
>> asyncronous communication is really really (really) cheap. I wouldn't
>> be suprised if told that the performance ratio is about or even over
>> 1000-1 between these operations.
>> If run time is not limiting for your simulations so far and if
>> emptying the process trash works for you, you can certainly continue
>> that way, but if time become limitating at some point, that's
>> certainly the feature that you want to leverage to solve your issue.
>> That's maybe not trivial to use, and certainly awfully
>> underdocumented, but it really helped us for the chord example.
> I'll start these modifications in my code on Monday, for sure.
> Simgrid-user mailing list
> Simgrid-user at lists.gforge.inria.fr
More information about the Simgrid-user