LOAD_PARAMETERS(5)

💖 LOAD_PARAMETERS(5) — the Grid Engine file formats girlies 💖

okay bestie, sit DOWN because we're talking about load_parameters — aka the Grid Engine default load parameters. this is the page about all the lil stats your execution daemon sge_execd(8) is out here reporting by default. no cap, it's a lot, but we're getting through it together 🫶

---

✨ NAME ✨

load_parameters — Grid Engine default load parameters 🌸

---

🌈 DESCRIPTION 🌈

so the load parameters that the execution daemon sge_execd(8) reports by default rn are literally these:

• arch — an architecture string that's compiled into the sge_execd, describing the operating system architecture the execd is targeted at. the possible values include:
  • aix51 — for IBM AIX 5.1, 5.3
  • darwin-x86 — for Apple Mac OS/X x86
  • darwin-ppc — for Apple Mac OS/X PowerPC
  • hp11 — for HP HP-UX 11.x 32-bit
  • hp11-64 — for HP HP-UX 11.x 64-bit
  • lx-amd64 — for GNU/Linux x86_64
  • lx-x86 — for GNU/Linux x86
  • sol-sparc64 — for Sun Solaris Sparc64
  • sol-x86 — for Sun Solaris x86
  • sol-amd64 — for Sun Solaris x86_64
  • win32-x86 — for Windows x86

heads up: an sge_execd for a particular architecture may run on multiple OS versions. in that case, the architecture string delivered by the execution daemon may be misleading. 💀 not me getting lied to by a string.

• num_proc — the number of processors the execution host provides. the host is defined by a single Internet address, i.e. rack mounted multi host systems are counted as a cluster rather than a single multi headed machine. in the case of "hardware threads" ("CMT" or "SMT"), normally num_proc is the number of such threads which are activated. 🔥

the following load info is only available under IBM AIX if Grid Engine is built with the perfstat library (which is now the default, bestie):

• load_short — the short time average OS run queue length. it's the first of the value triple reported by uptime(1). many implementations provide a 1 minute average with this value.
• load_medium — the medium time average OS run queue length. it's the second of the value triple reported by uptime(1). many implementations provide a 5 minute average with this value.
• load_long — the long time average OS run queue length. it's the third of the value triple reported by uptime(1). many implementations provide a 10 or 15 minute average with this value.
• load_avg — the same as load_medium.
• np_load_short — the same as load_short but divided by the number of processors. this value allows comparing the load of single and multi-headed hosts. 🧚
• np_load_medium — the same as load_medium but divided by the number of processors. this value allows comparing the load of single and multi-headed hosts.
• np_load_long — the same as load_long but divided by the number of processors. this value allows comparing the load of single and multi-headed hosts.
• np_load_avg — the same as load_avg but divided by the number of processors. this value allows comparing the load of single and multi-headed hosts.
• cpu — the percentage of CPU time not in idle state. 💅

and ALSO (yes there's more, the AIX girls are eating good) — the following load information is only available under IBM AIX if Grid Engine is built with the perfstat library (which is now the default):

• mem_free — the amount of free real memory.
• swap_free — the amount of free swap memory.
• virtual_free — the sum of mem_free and swap_free.
• mem_used — the amount of memory used.
• swap_used — the amount of swap space used.
• virtual_used — the sum of mem_used and swap_used.
• mem_total — the total amount of memory (free+used).
• swap_total — the total amount of swap space (free+used).
• virtual_total — the sum of mem_total and swap_total.

the following load information is ONLY available under Windows 👑 (capital letters, so you KNOW it's serious):

• display_win_gui — the host is capable of displaying the GUI of a Windows job.

the following load information is only available if Grid Engine was built with the hwloc library (the default) and if hwloc supports the system. 🦋

• m_topology_inuse — the host cpu topology string reported by an execution host. this might be "NONE" if the topology cannot be determined; otherwise it's a string consisting of the upper and lowercase letters "S", "C", "T", "c", and "t". the sequence of letters within that string represents the hardware topology where "S" represents a socket, "C" or "c" a core, and "T" or "t" a hardware thread.

the string "SCCSCCSCCSCC" will returned by a host that has 4 sockets where each of those sockets has two cores. all cores are available because all "C"s appear in capital letters.

if lowercase letters are used then this means that the corresponding core or thread is already in use because there is at least one running Grid Engine job bound to it.

"SCCSCcSCCscc" means that core 2 on socket 2 and also core 1 and core 2 on socket 4 are in use. 😭 (rip those cores, they're booked and busy)

• m_topology — like m_topology_inuse, except that it represents the architecture, not the use of it, i.e. it doesn't contain lower case letters.
• m_socket — number of sockets available on the reporting host (e.g. "SCCSCCSCCSCC" => m_socket=4)
• m_core — number of cores reported for all sockets on a host (e.g. "SCCSCCSCCSCC" => m_core=2)
• m_thread — number of hardware threads reported for all cores on a host, which should be equal to num_proc (e.g. "SCTTCTTCTTCTT" => m_thread=8)

---

⭐ Static Load Values ⭐

the "static" load values (which may be selected with qhost -l or qselect -l) are: arch, num_proc, mem_total, swap_total, virtual_total, m_topology, m_socket, m_core, m_thread.

like, that's the whole list. memorize it, it's giving flashcard energy. 📝

---

💜 SEE ALSO 💜

complex(5), sge_execd(8).

---

and that's the whole page bestie!! 🎀 this one's from SGE 8.1.3pre, dated $Date: 2011-12-04 12:16:31 $ — yes she's an elder but she ATE and left no crumbs. go forth and read your load parameters, ily, bye!! 💅✨🦋