resource_...histograms(1)

💖 resource_monitor_histograms — bestie edition 💖

okay so this is the resource_...histograms(1) page from the Cooperative Computing Tools manual, and I'm about to explain it to you like we're texting at 2am. it's genuinely useful, no cap.

---

✨ NAME ✨

resource_monitor_histograms — make HTML pages and graphs out of your resource monitor data 🎀

---

🌸 SYNOPSIS 🌸

resource_monitor_histograms [options] -L monitor_data_file_list
output_directory [workflow_name] resource_monitor_histograms [options]
output_directory < monitor_data_file_list  [workflow_name]

---

🦋 DESCRIPTION 🦋

so resource_monitor_histograms is literally the glow-up machine for your resource usage. it takes what resource_monitor reported and turns it into something you can actually look at. 👑

here's the vibe: it wants a file that lists the paths of your summary files. you can hand it that list either with the -L option or by piping it in from standard input. either way, it eats the list.

then it writes the results into output_directory, and what lands there is a whole set of webpages — histograms and statistics for each resource. it's giving data visualization era. 💅

---

🌈 ARGUMENTS 🌈

💜 Input Options

• -L <monitor_data_file_list> — a file with one summary file path per line. that's it, that's the job. 🍓

🧚 Output Options

• output_directory — the path where the visualizations get stored. go look at index.html for the root of the whole visualization, that's your entry point bestie. 🫶
• workflow_name — optional! a name you can include to describe the workflow being visualized. cute little label energy. ✨
• -f <str> — pick which fields you want histograms for. default is "cores,memory,disk". and here are ALL the available fields, no skipping:
  • bandwidth
  • bytes_read
  • bytes_received
  • bytes_send
  • bytes_written
  • cores
  • cpu_time
  • disk
  • max_concurrent_processes
  • memory
  • swap_memory
  • total_files
  • total_processes
  • virtual_memory
  • wall_time

🔥 Debugging Options

• -d, --debug=<subsystem> — turn on debugging for this subsystem. go off. 🔍
• -o, --debug-file=<file> — write debugging output to this file instead. by default debugging goes to stderr (":stderr"), but you can also send logs to stdout (":stdout") if that's more your thing.
• --verbose — show runtime progress on stdout. main character update feed. 💀

---

⭐ EXAMPLES ⭐

the most common usage, aka the classic:

% find my_summary_files_directory -name "*.summary" > summary_list
% resource_monitor_histograms -L summary_list my_histograms my_workflow_name
% # open my_histograms/index.html

and if you wanna split on categories and only get the resident memory related histograms:

% resource_monitor_histograms -f memory -L summary_list my_histograms my_workflow_name
% # open my_histograms/index.html

---

👑 COPYRIGHT 👑

The Cooperative Computing Tools are Copyright (C) 2005-2019 The University of Notre Dame. This software is distributed under the GNU General Public License. See the file COPYING for details.

fr fr, read the COPYING file, it's the whole legal situation, don't skip it. 🙈

---

okay that's the whole page, you ate it, periodt. 💅 this was CCTools 8.0.0 DEVELOPMENT — the resource_...histograms(1) manual page, from the Cooperative Computing Tools. love u, go make some histograms 🎀💖✨