{"id":156,"date":"2020-03-01T11:15:30","date_gmt":"2020-03-01T16:15:30","guid":{"rendered":"http:\/\/localhost:8080\/?p=156"},"modified":"2024-05-21T11:11:53","modified_gmt":"2024-05-21T15:11:53","slug":"getting-information-about-the-clusters-and-your-jobs","status":"publish","type":"post","link":"https:\/\/knowledgebasev.kinsta.cloud\/?p=156","title":{"rendered":"2) All about Cores, Compute Nodes, and Clusters"},"content":{"rendered":"

Cores, Compute Nodes, Clusters, and other Resources<\/span><\/h2>\n

Terminology\u00a0<\/strong><\/h3>\n

ssClient, Client, Login Client –<\/strong>\u00a0The application you downloaded and installed. Sometimes referred as “ssClient”, client, or login client. This is were you enter commands, transfer files, and launch and access the remote desktop.<\/p>\n

Job<\/strong>\u00a0– A user’s work load or process; what the user wants to run, process, simulate.<\/p>\n

Core<\/strong> – A \u201ccore\u201d is one physical processor of a CPU. A CPU core is a CPU\u2019s processor. A CPU has many cores.\u00a0You can think of a core as a single processor. For example, if you need “32 processors” for a job, you\u00a0need 32 cores.<\/p>\n

CPU<\/strong> – A CPU contains many processor cores.<\/p>\n

Compute node<\/strong> – A \u201ccompute node\u201d (also referred to as \u2018node\u2019) is a server with 2 CPUs, memory, local storage, networked storage, and a high performance network connection to other compute nodes in the cluster. Jobs run on one or more compute nodes.<\/p>\n

Cluster<\/strong> – Compute nodes of similar configuration are organized into \u201cclusters\u201d. Each cluster has a name to easily identify it. For example, these are names of some of the clusters: “blue”, “copper”, “red”.<\/p>\n

Terminal<\/strong> –\u00a0A terminal accepts command line inputs (ie CLI). The terminal is also available in the remote graphics (i.e. remote desktop).\u00a0 The ssClient\/ login client is also a in fact a terminal. You can enter any command-line command at the prompt in the\u00a0client.<\/p>\n

\"\"<\/p>\n

What processors, compute nodes, and clusters are available?<\/strong><\/h3>\n

When a job is submitted for processing, it is placed in a queue. The job will start on the first available\u00a0node directive specified by the job parameters. Regardless of how busy a particular cluster is, the job will start when the resources become available.<\/p>\n

upnodes<\/span> – The \u201cupnodes\u201d command gives a quick and simple overview table of the clusters and their compute node configurations (and current status) .\u00a0 The cluster name (which you will\u00a0need to use to specify cores), processor type, RAM, and total number of nodes and cores in the cluster are displayed in the table. Use this information to help determine your job’s node directive<\/a>\u00a0described in\u00a0artical\u00a04<\/a>\u00a0“Setting up your Job” of this section or if you are using a launcher to select your cores.<\/p>\n

Try this –> In any terminal, enter the command “upnodes” at the prompt.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

Upper Section\u00a0–<\/strong><\/span> In the first section of the output, the first row of the table contains the “cluster” names. The column beneath the cluster name are the cluster details.<\/p>\n