Trinity Runtime Profiling

Brian Haas edited this page Feb 18, 2017 · 5 revisions
Clone this wiki locally

Examining Resource Usage at the End of a Trinity Run

To examine a summary report of resources consumed during a complete run of Trinity, you can run Trinity with the '--monitoring' parameter. This will cause Trinity to run the collectl alongside of it to capture resource usage statistics. Collectl polls the operating system to examine CPU, memory, and I/O usage and we capture those data at regular intervals (defined by the Trinity parameter '--monitor_sec', default set to 60 seconds).

The resource usage statistics are collected in a file that is written to '${PWD}/collectl/collectl.dat'. You can generate a report summary and a viewable plot of resource usage vs. time by running the following once the Trinity job has completed:

  $TRINITY_HOME/trinity-plugins/COLLECTL/ collectl

Note, be sure to run this in your original working directory that contains the collectl/ subdirectory.

This will generate output files:




View the pdf to examine the resource usage vs. run time. For example, here's the progress monitoring view for processing 10M PE 76 base mouse fastq files through Trinity, showing the resource usage as a function of time (hours).

and another example using 50 M PE reads: