Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Pitoiset <samuel.pitoiset@inria.fr>
- To: Alfredo Buttari <alfredo.buttari@enseeiht.fr>, starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] help with trace.rec and tasks.rec
- Date: Tue, 6 Sep 2016 14:03:16 +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>
Hi,
On 09/06/2016 01:54 PM, Alfredo Buttari wrote:
Hello,
for some reason I am getting no "Task" events in the trace.rec file. As
a result, the starpu_trace_state_stats.py is printing something like
this (obtained running examples/cholesky/cholesky_grain_tag -size 2048)
$ starpu_trace_state_stats.py trace.rec | column -t -s ","
"Name" "Count" "Type" "Duration"
"Initializing" 2 "Runtime" 0.108658
"Overhead" 4538 "Runtime" 79.911275
"Idle" 1514 "Other" 0.579661
"Scheduling" 3024 "Runtime" 1.635756
"Sleeping" 28 "Other" 52.331106
"FetchingInput" 1512 "Runtime" 1.332104
"PushingOutput" 1512 "Runtime" 0.807078
"Submitting task" 1512 "User" 1.968799
am I doing anything wrong? Second question, is there any tool to parse
the tasks.rec file? In what should the tasks.rec and trace.rec files differ?
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 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.
Ciao
Alfredo
--
-----------------------------------------
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
- [Starpu-devel] help with trace.rec and tasks.rec, Alfredo Buttari, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Samuel Pitoiset, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Alfredo Buttari, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Samuel Pitoiset, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Samuel Pitoiset, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Alfredo Buttari, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Samuel Pitoiset, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Alfredo Buttari, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Samuel Pitoiset, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Alfredo Buttari, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Samuel Pitoiset, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Samuel Pitoiset, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Alfredo Buttari, 06/09/2016
- Re: [Starpu-devel] help with trace.rec and tasks.rec, Samuel Pitoiset, 06/09/2016
Archives gérées par MHonArc 2.6.19+.