huttered40 / critter

Critical path analysis of MPI parallel programs
BSD 2-Clause "Simplified" License
2 stars 1 forks source link

Improve output visualization #58

Closed huttered40 closed 3 years ago

huttered40 commented 4 years ago
  1. Print out the environment variable file name before the measurement data
  2. List the differences in critical-path data next to eachother, rather than in separate sections
  3. Add an extra internal timer in critter::start and completing in critter::stop to measure the total time taken, so we can detect the raw overhead critter incurs