Objet : Developers list for StarPU
Archives de la liste
- From: Xavier Lacoste <xavier.lacoste@inria.fr>
- To: starpu-devel@lists.gforge.inria.fr
- Cc: Mathieu Faverge <Mathieu.Faverge@inria.fr>, Pierre Ramet <ramet@labri.fr>
- Subject: [Starpu-devel] memory overhead
- Date: Fri, 6 Dec 2013 14:52:59 +0100
- List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel>
- List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>
Hello,
I'm studying memory overhead with StarPU/ParSEC/native scheduler in PaStiX and i noticed a slightly bigger oerhead with StarPU.
I also noticed a very very large number of allocation with StarPU 1.1 (r11396M) (from eztrace report).
Here are two figures, the first one is the memory peak with the schedulers overhead in blue/red/beige, and the ratio compared to PaStiX peak on top, the second the number of allocations obtained during the run.
This is obtained with the direct linear solver PaStiX on 9 different matrices tests cases, on 12 cores on mirage.
Have you go an idea of what could explain this overhead (+8% compared to PaStiX peak but much more if we don't take into account common data structures, which may be a more interesting metric....) and the huge number of calls to malloc().
Regards,
XL.
----------------------------------------
Xavier Lacoste
INRIA Bordeaux Sud-Ouest
200, avenue de la Vieille Tour
33405 Talence Cedex
Tél : +33 (0)5 24 57 40 69
- [Starpu-devel] memory overhead, Xavier Lacoste, 06/12/2013
- Re: [Starpu-devel] memory overhead, Samuel Thibault, 12/12/2013
Archives gérées par MHonArc 2.6.19+.