DETERMINE_MAXIMUM_MPPS(8)

💖 DETERMINE_MAXIMUM_MPPS 💖

okay bestie, so this one lives in section 8 of the System Manager's Manual, and it's literally the tool that goes "how many million packets per second can this machine actually handle tho" 🦋

---

✨ NAME ✨

determine_maximum_mpps — figure out the maximum mpps your machine can handle, no cap

---

🌸 SYNOPSIS 🌸

determine_maximum_mpps [-a cpulist] [-m maxlat] [-n cycles] [-f | -r]
                       [-p priority] [-h]

---

👑 DESCRIPTION 👑

determine_maximum_mpps is gonna hunt down the maximum mpps parameter that can sustain:

1. 10 consecutive 30 second runs.
2. 1 run of 10 minutes.

...all while not violating the latency you set with $MAXLAT (default 20000). she's thorough, she's patient, she's doing the most and we love her for it 💅

---

🎀 TERMINOLOGY 🎀

• mpps : million-packets-per-second

---

✨ OPTIONS ✨

• -a cpulist — the list of processors to run on. default is processor 0. numbers are separated by commas and may include ranges. eg. 0,3,7-11
• -m maxlat — maximum latency in nanoseconds. the default is 20000. if the maximum is exceeded, that run of queuelat quits. 😭
• -n cycles — extimated number of cycles it takes to process one packet. (yes, "extimated", we keep it exactly as written, periodt ✨) the default is 300
• -f — set the scheduling policy to SCHED_FIFO. this is the default if not specified.
• -r — set the scheduling policy to SCHED_RR.
• -p priority — default priority = 1. valid numbers are from 1 to 99
• -h — help 🫶

---

🌈 AUTHOR 🌈

determine_maximum_mpps was written by Marcelo Tosatti <mtosatti@redhat.com>

This man page was written by John Kacur <jkacur@redhat.com>

---

and that's the whole thing bestie 💜 the SPDX license tag on this page is GPL-2.0-or-later, and the page itself is dated Dec 4, 2020 — so yeah, iconic, timeless, a little vintage, but she still slays 🔥⭐🍓