GETDELAYS(1)

📦 version 6.12.0, in opensuse-leap 16.0

💅 GETDELAYS — it's a whole general commands manual moment

okay bestie, so this is getdelays(1) from the General Commands Manual and it's genuinely iconic for anyone whose app is being slow and mysterious ✨

✨ NAME ✨

getdelays — display delay statistics 🎀

🦋 SYNOPSIS 🦋

getdelays -c  command
getdelays -p  pid
getdelays -t  tid

three modes, three vibes, pick your fighter 💖

🌸 DESCRIPTION 🌸

So the getdelays utility is literally here to help you pin-point possible resource shortages when you're running an application. Like, when your program is out here struggling and you don't know why? This is the tool. 🔍

The SLES10 kernel includes patches to implement delay accounting, which measures the time a process spends waiting for disk I/O, swap I/O and CPU time slices. Obsessed with her honestly. So for example, if an application is running rather slowly, delay accounting can tell you where it spends all its time. main character diagnostics ✨

For instance, when the CPU delay is high, this means the application is competing with other proces for run time, but is losing quite often. 😭 (yes the manpage says "proces" and we respect the typo, it's canon now)

High memory delays mean that the sum of applications running on this system need more physical memory than is available, and are swapping quite a lot. ngl that's giving "your RAM said no" 💀

🫶 important vibe check: in order to enable delay accounting, you need to specify delayacct on the kernel command line when booting the system. no delayacct, no stats. periodt.

Getdelays has three modes of operation, and here they are bestie:

🌈 the three modes

  • getdelays -c command — this will invoke command and print a summary of delay statistics when the command finishes. set it and forget it, she reports back at the end 💅
  • getdelays -p pid — this will print the current delay statistics of the process identified pid. little snapshot moment 📸
  • getdelays -t tid — this will print the current delay statistics of the thread group identified tid. yes, thread group, she's not doing single threads, she's doing the whole group 🧚

👑 AUTHOR 👑

  • Balbir Singh, IBM Corp.
  • Shailabh Nagar, IBM Corp.
  • Manpage contributed by Olaf Kirch <okir@suse.de>

and that's the whole page bestie, no cap 🎀 this little gem is dated April 13, 2006 and it's still serving delay-accounting realness to this very day — courtesy of that general commands manual energy, go off 💜🔥

📦 where this page comes from