> For the complete documentation index, see [llms.txt](https://documentation.tjhsst.edu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.tjhsst.edu/machines/hpc-cluster.md).

# HPC Cluster

The **HPC Cluster** is the CSL's main **H**igh **P**erformance **C**omputing Cluster.

**It should only be accessed through** [Slurm](/services/cluster/slurm.md)! See the page on [Cluster](/services/cluster.md) for more details.

## Technical Specifications

There are 12 nodes in the cluster, each part of a 4-node SuperMicro 4U SuperBlade, each with the same specifications:

| **Specification** | Description                           |
| ----------------- | ------------------------------------- |
| **Server Type**   | SuperMicro 4U SuperBlade              |
| **CPU**           | Intel(R) Xeon(R) E5-2630 v2 @ 2.60GHz |
| **RAM**           | 64 GB                                 |
| **Hard Disks**    | 2x 250GB RAID 1                       |
| **OS**            | Ubuntu 24.04 (as of June 2026)        |
| **Purchase Date** | 2016                                  |

## Trivia

Each of the nodes in the HPC cluster is named after a [robot from Futurama](https://en.wikipedia.org/wiki/List_of_Futurama_characters), making them hard to remember (although not nearly as hard as the [Borg Cluster](/machines/borg-cluster.md)!).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.tjhsst.edu/machines/hpc-cluster.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.