|
@@ -209,7 +209,7 @@ $ dot -Tpdf dag.dot -o output.pdf
|
|
|
|
|
|
Another generated trace file gives details on the executed tasks. The
|
|
|
file, created in the current directory, is named <c>tasks.rec</c>. This file
|
|
|
-is in the recutils format, i.e. <c>Field: value</c> lines, and empty lines to
|
|
|
+is in the recutils format, i.e. <c>Field: value</c> lines, and empty lines are used to
|
|
|
separate each task. This can be used as a convenient input for various ad-hoc
|
|
|
analysis tools. By default it only contains information about the actual
|
|
|
execution. Performance models can be obtained by running
|
|
@@ -231,6 +231,14 @@ Another possibility is to obtain the performance models as an auxiliary <c>perfm
|
|
|
$ starpu_perfmodel_recdump tasks.rec -o perfmodel.rec
|
|
|
\endverbatim
|
|
|
|
|
|
+\subsubsection TraceSchedTaskDetails Getting Scheduling Task Details
|
|
|
+
|
|
|
+The file, <c>sched_tasks.rec</c>, created in the current directory,
|
|
|
+and in the recutils format, gives information about the tasks
|
|
|
+scheduling, and lists the push and pop actions of the scheduler. For
|
|
|
+each action, it gives the timestamp, the job priority and the job id.
|
|
|
+Each action is separated from the next one by empty lines.
|
|
|
+
|
|
|
\subsubsection MonitoringActivity Monitoring Activity
|
|
|
|
|
|
Another generated trace file is an activity trace. The file, created
|