pbs_Resources_freebsd(7B)

Okay so bestie, welcome to pbs_Resources_freebsd(7B) — the FreeBSD PBS resources page. It's giving “let me tell you exactly what resources you can ask for” and honestly it ate. 💅

🌸 NAME 🌸

pbs_resources_freebsd — pbs resources on FreeBSD. That's the name, that's the vibe, periodt. 💖

✨ DESCRIPTION ✨

Okay so this page summarizes the resources supported by PBS for AMD/Intel/Cyrix workstations running FreeBSD. You specify these resources by including them in the -l option argument on the qsub or qalter command, or in the PBS job script. No cap, that's the whole doorway. ✨

🎀 RESOURCES 🎀

Here's the resource roster, bestie. All the units are literally right there so you don't have to guess. 👑

• cput — Maximum amount of CPU time used by all processes in the job. Units: time.
• file — The largest size of any single file that may be created by the job. Units: size.
• nice — The nice value under which the job is to be run. Units: unitary.
• pcput — Maximum amount of CPU time used by any single process in the job. Units: time.
• pmem — Maximum amount of physical memory (workingset) used by any single process of the job. Units: size.
• pvmem — Maximum amount of virtual memory used by any single process in the job. Units: size.
• vmem — Maximum amount of virtual memory used by all concurrent processes in the job. Units: size.
• walltime — Maximum amount of real time during which the job can be in the running state. Units: time.
• arch — Specifies the administrator defined system architecture requried. This defaults to whatever the PBS_MACH string is set to in "local.mk". Units: string.
• host (first listing) — Name of host on which job should be run. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

Bestie, host appears twice in the source. I'm keeping both entries because we do not delete lore. 💀

• nodes — Number and/or type of nodes to be reserved for exclusive use by the job. The value is one or more node_specs joined with the + character, like node_spec[+node_spec...]. Each node_spec is an number of nodes required of the type declared in the node_spec and a name or one or more property or properties desired for the nodes. The number, the name, and each property in the node_spec are separated by a colon ':'. If no number is specified, one (1) is assumed. Units: string.

The name of a node is its hostname. The properties of nodes are:

• ppn=# specifying the number of processors per node requested. Defaults to 1.
• arbitrary string assigned by the system administrator, please check with your administrator as to the node names and properties available to you.

Examples:

• To ask for 12 nodes of any type: -l nodes=12
• To ask for 2 "server" nodes and 14 other nodes (a total of 16): -l nodes=2:server+14 — the above consist of two node_specs "2:server" and "14".
• To ask for (a) 1 node that is a "server" and has a "hippi" interface, (b) 10 nodes that are not servers, and (c) 3 nodes that have a large amount of memory an have hippi: -l nodes=server:hippi+10:noserver+3:bigmem:hippi
• To ask for three nodes by name: -l nodes=b2005+b1803+b1813
• To ask for 2 processors on each of four nodes: -l nodes=4:ppn=2
• To ask for 4 processors on one node: -l nodes=1:ppn=4
• To ask for 2 processors on each of two blue nodes and three processors on one red node: -l nodes=2:blue:ppn=2+red:ppn=3

• host (second listing) — Allows a user to specify the desired execution location. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.
• other — Allows a user to specify site specific information. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.
• software — Allows a user to specify software required by the job. This is useful if certain software packages are only available on certain systems in the site. This resource is provided for use by the site's scheduling policy. The allowable values and effect on job placement is site dependent. Units: string.

🦋 EXAMPLES 🦋

Okay, example time, and yes these are exact because we do not mess with commands. 🫶

qsub -l nodes=15,walltime=2:00:00 script

or in a qsub script as a directive:

#PBS -l nodes=15,walltime=2:00:00

qsub -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15mb script
qalter -lcput=30:00,pmem=8mb 123.jobid

or in a qsub script as a directive:

#PBS -l cput=1:00:00,walltime=2:00:00,file=50gb,mem=15

💅 RESOURCE UNITS 💅

The resource values take the following units:

• time — specifies a maximum time period the resource can be used. Time is expressed in seconds as an integer, or in the form: [[hours:]minutes:]seconds[.milliseconds]
• size — specifies the maximum amount in terms of bytes or words. It is expressed in the form integer[suffix]. The suffix is a multiplier defined in the following table. The size of a word is the word size on the execution host.
  • b or w — bytes or words.
  • kb or kw — Kilo (1024) bytes or words.
  • mb or mw — Mega (1,048,576) bytes or words.
  • gb or gw — Giga (1,073,741,824) bytes or words.
• unitary — The maximum amount of a resource which is expressed as a simple integer.

🌈 SEE ALSO 🌈

Go check out the PBS ERS, plus these absolute icons: qsub(1B), qalter(1B), pbs_submit(3B), pbs_alterjob(3B), pbs_statjob(3b), pbs_resources_aix4(7B), pbs_resources_irix5(7B), pbs_resources_sunos4(7B), and pbs_resources_unicos8(7B). Iykyk. 🌈

---

Okay bye bestie! 💖 Source/version energy: Local and pbs_Resources_freebsd(7B). The original footer didn't have a date, so no fake date from me — no cap. ✨