SimGrid  3.15
Versatile Simulation of Distributed Systems
TRACING

Detailed Description

Gather data about your simulation for later analysis.

SimGrid can trace the resource (of hosts and links) utilization using any of its programming interfaces (MSG, SimDAG and SMPI). This means that the tracing will register how much power is used for each host and how much bandwidth is used for each link of the platform.

The idea of the tracing facilities is to give SimGrid users to possibility to classify MSG and SimDAG tasks by category, tracing the platform utilization (hosts and links) for each of the categories. The API enables the declaration of categories and a function to associate them to the tasks (MSG and SD). The tasks that are not classified according to a category are not traced. If no categories are specified, simulations can still be traced using a special parameter in the command line (see Visualization and Statistical Analysis for details).

TRACE documentation

Modules

 Tracing categories
 Functions to declare tracing categories.
 
 Tracing marks
 Functions to declare and create tracing marks.
 
 Tracing user variables
 Functions to declare and define user variables associated to resources.
 

Functions

int TRACE_platform_graph_export_graphviz (const char *filename)
 Creates a file with the topology of the platform file used for the simulator. More...
 
xbt_dynar_t TRACE_get_node_types ()
 Get Paje container types that can be mapped to the nodes of a graph. More...
 
xbt_dynar_t TRACE_get_edge_types ()
 Get Paje container types that can be mapped to the edges of a graph. More...
 
void TRACE_pause ()
 Pauses all tracing activities. More...
 
void TRACE_resume ()
 Resumes all tracing activities. More...
 

Function Documentation

◆ TRACE_platform_graph_export_graphviz()

int TRACE_platform_graph_export_graphviz ( const char *  filename)

Creates a file with the topology of the platform file used for the simulator.

The graph topology will have the following properties: all hosts, links and routers of the platform file are mapped to graph nodes; routes are mapped to edges. The platform's AS are not represented in the output.

Parameters
filenameThe name of the file that will hold the graph.
Returns
1 of successful, 0 otherwise.

◆ TRACE_get_node_types()

xbt_dynar_t TRACE_get_node_types ( )

Get Paje container types that can be mapped to the nodes of a graph.

This function can be used to create a user made graph configuration file for Triva. Normally, it is used with the functions defined in Tracing user variables.

Returns
A dynar with the types, must be freed with xbt_dynar_free.

◆ TRACE_get_edge_types()

xbt_dynar_t TRACE_get_edge_types ( )

Get Paje container types that can be mapped to the edges of a graph.

This function can be used to create a user made graph configuration file for Triva. Normally, it is used with the functions defined in Tracing user variables.

Returns
A dynar with the types, must be freed with xbt_dynar_free.

◆ TRACE_pause()

void TRACE_pause ( )

Pauses all tracing activities.

See also
TRACE_resume

◆ TRACE_resume()

void TRACE_resume ( )

Resumes all tracing activities.

See also
TRACE_pause