Re: [Starpu-devel] help with trace.rec and tasks.rec

[Samuel Pitoiset <samuel.pitoiset@inria.fr>]

Please update your repo. The following commit should help. :)

commit be211beddfa10db55d829cca70f7084692b8763f
Author: spitoiset <spitoiset@176f6dd6-97d6-42f4-bd05-d3db9ad07c7a>
Date:   Tue Sep 6 12:32:39 2016 +0000

    debug/traces: always dump codelet details to trace.rec

    When no paje.trace file is generated, codelet details (ie. Task states)
    were not dumped to trace.rec. This has been reported by Alfredo 
Buttari.


On 09/06/2016 02:22 PM, Samuel Pitoiset wrote:
> On 09/06/2016 02:16 PM, Alfredo Buttari wrote:
> > Samuel,
> > thanks for the quick answer. See below
> >
> > On Tue, Sep 6, 2016 at 2:03 PM, Samuel Pitoiset
> > <samuel.pitoiset@inria.fr <mailto:samuel.pitoiset@inria.fr>> wrote:
> >
> >     Weird. I have just tried locally and the output for me looks like:
> >
> >     $ python2.7 tools/starpu_trace_state_stats.py trace.rec | column -t
> >     -s ","
> >     "Name"             "Count"  "Type"     "Duration"
> >     "Initializing"     4        "Runtime"  1.036028
> >     "Overhead"         4540     "Runtime"  5.291885
> >     "Idle"             1516     "Other"    0.60503
> >     "Scheduling"       3026     "Runtime"  1.346616
> >     "Sleeping"         30       "Other"    88.045689
> >     "FetchingInput"    1512     "Runtime"  0.961838
> >     "chol_model_21"    212      "Task"     100.915113 ---> This is what
> >     you want!
> >     "PushingOutput"    1512     "Runtime"  0.587924
> >     "chol_model_22"    1276     "Task"     890.891958
> >     "chol_model_11"    24       "Task"     3.280441
> >     "Submitting task"  1512     "User"     1.506503
> >
> >     This is with starpu-svn from today or yesterday.
> >
> >     Which version are you using?
> >
> >
> > I am using the latest revision of the trunk. Is there any configure
> > option or (at runtime) any environment variable I have to set?
>
> I used:
> STARPU_GENERATE_TRACE=1 examples/cholesky/cholesky_grain_tag -size 2048
>
> Mmmh, you might need to build StarPU with Fxt (cf. --with-fxt=<dir>)
> because trace.rec is quite related to paje.trace actually (a bunch of
> similar code are shared).
>
> Is there a paje.trace generated after the execution?
>
> >     I don't remember how to parse the tasks.rec, maybe there is a tool
> >     in trunk/tools, not sure though.
> >
> >     The main difference between tasks.rec and trace.rec is that the
> >     former contains more information about the tasks and the latter only
> >     contains the different states of the execution.
> >
> >
> > thanks for the details.
> >
> >
> > --
> > -----------------------------------------
> > Alfredo Buttari, PhD
> > CNRS-IRIT
> > 2 rue Camichel, 31071 Toulouse, France
> > http://buttari.perso.enseeiht.fr
> _______________________________________________
> Starpu-devel mailing list
> Starpu-devel@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/mailman/listinfo/starpu-devel