Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: Jeff DiMarco <jdimarco218@gmail.com>
- Cc: "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>
- Subject: Re: [Starpu-devel] About Paje trace generation
- Date: Tue, 18 Jun 2013 22:25:32 +0200
- 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,
Jeff DiMarco, le Tue 18 Jun 2013 21:42:35 +0200, a écrit :
> I am working on analyzing the resulting Paje traces that StarPU produces
> with
> my heterogeneous applications. Specifically, I would like to find the
> critical
> path of the execution of my application. My initial guess was that the
> PajeLinks would be created for task dependencies, but they are not.
Indeed, we don't record task dependencies in the paje output. What you
can use instead is the .dot output, see the “Creating a DAG With
Graphviz” section of the documentation.
Samuel
- [Starpu-devel] About Paje trace generation, Jeff DiMarco, 18/06/2013
- Re: [Starpu-devel] About Paje trace generation, Samuel Thibault, 18/06/2013
Archives gérées par MHonArc 2.6.19+.