# Single AMD EPYC 7713P Sled

## Can High-Compute, Multiprocessor-Designed Software Run Well on a Single AMD EPYC 7713P Sled?

### 1. **Processor Overview**

The **AMD EPYC 7713P** is a **single-socket CPU** with:

* **64 physical cores**
* **128 threads** (with SMT)
* High memory bandwidth and PCIe lanes

This is a **very high-core-count processor**, making it one of the most capable CPUs for multi-threaded workloads in a single socket.

***

### 2. **Running Multiprocessor-Designed Software**

#### **A. Multiprocessor vs. Multicore**

* **Multiprocessor software** is often written to scale across multiple CPU sockets (NUMA nodes).
* **Multicore software** is written to use many threads, regardless of whether they are on one or multiple sockets.

The AMD EPYC 7713P, despite being single-socket, provides a NUMA-like environment internally (multiple chiplets), but all within one physical processor.

#### **B. Compatibility**

* **Most modern high-performance software** (like HiGHS Optimization, Julia, scientific computing libraries, databases, etc.) will **run extremely well** on a single EPYC 7713P, provided they are designed for multi-threading or parallelism.
* **Software expecting multiple physical CPUs** (true multi-socket NUMA) may see some differences in memory access patterns, but the EPYC 7713P’s internal architecture is designed to minimize these issues.

#### **C. Potential Issues**

* **Licensing/Configuration:** Some software licenses or configurations are tied to the number of sockets, not cores. Make sure your software is configured to use all available cores/threads.
* **Thread Scaling:** Some legacy software may not scale efficiently beyond a certain number of threads, but most modern libraries (like HiGHS or Julia) scale well to 64+ cores.

***

### 3. **Managing High Compute Performance Requirements**

#### **A. HiGHS Optimization C Libraries**

* **HiGHS** is designed for multi-threaded optimization and can use all available cores.
* On a 64-core/128-thread EPYC, you can set the number of threads to match the physical or logical cores for maximum throughput.
* **Best Practice:** Set the thread count in HiGHS to match your workload and system resources (`OMP_NUM_THREADS=64` for physical cores, or up to 128 for SMT).

#### **B. Julia Runtimes**

* Julia is highly parallel and can take advantage of all available cores.
* Use the `-t` or `--threads` flag to specify the number of threads (e.g., `julia -t 64`).
* For distributed computing, Julia can also launch multiple processes, each using multiple threads, all within a single sled.

#### **C. General Recommendations**

* **Tune thread affinity:** Bind threads to cores to minimize context switching and cache misses.
* **Monitor NUMA effects:** While a single EPYC socket, internal NUMA domains (chiplets) exist. Use tools like `numactl` or `hwloc` to optimize memory locality if needed.
* **Profile your workload:** Use performance tools (e.g., `htop`, `perf`, `numastat`) to ensure you’re utilizing all cores efficiently.

***

## **Summary Table**

| Software Type          | Will it run well on 1× EPYC 7713P? | Notes/Recommendations                        |
| ---------------------- | :--------------------------------: | -------------------------------------------- |
| HiGHS Optimization     |                 Yes                | Set thread count to match cores/threads      |
| Julia (multi-threaded) |                 Yes                | Use `-t` flag for threads; consider affinity |
| General HPC/Parallel   |                 Yes                | Optimize for NUMA if needed                  |

***

## **Conclusion**

**Yes, special high-compute, multiprocessor-designed software will generally run very well on a single AMD EPYC 7713P CPU in one Oxide sled.** You have 64 physical cores (128 threads), which is more than most dual-socket systems of previous generations. For best results:

* Set thread counts appropriately,
* Monitor and tune for NUMA locality if needed,
* Profile and optimize your workload for the specific architecture.

**You will not face fundamental issues with multi-threaded software on a single sled—modern high-core CPUs like the EPYC 7713P are built for exactly these scenarios.**

Sources \[1] Oxide-Rack-Specifications-20250217.pdf <https://ppl-ai-file-upload.s3.amazonaws.com/web/direct-files/attachments/49592179/789ab338-90b7-4640-8b69-a93309ad4204/Oxide-Rack-Specifications-20250217.pdf>

<https://www.perplexity.ai/search/9bb0a0e4-0954-4978-915f-02d3c37e5fb0>

#### Other resources & links

* [Oxide CDS Usage Breakdown](https://book.univrs.io/markd/oxide_cds_usage_breakdown)
* [oxide CDS Usage v2](https://book.univrs.io/markd/oxide_cds_v2)
* [Oxide Innovation](https://book.univrs.io/markd/oxide_innovations)
* [Oxide OS+Hardware](https://book.univrs.io/markd/oxide_os-hardware)
* [Oxide Rack Customers](https://book.univrs.io/markd/oxide_rack_customers)
* [Oxide Single AMD EPYC 7713P](https://book.univrs.io/markd/oxide_single_amd_epyc_7713p_sled)
* [Oxide Smallest Bang$](https://book.univrs.io/markd/oxide_smallest_possible_sled)
* [Oxide Syndrom](https://book.univrs.io/markd/oxide_syndrome)

### Connect: Join Univrs.io

* [Univrs.io Discord](https://discord.gg/pXwH6rQcsS)
* [Univrs Patreon](https://www.patreon.com/univrs)
* [Univrs.io](https://univrs.io)
* <https://ardeshir.io>
* <https://hachyderm.io/@sepahsalar>
* <https://github.com/ardeshir>
* <https://medium.com/@sepahsalar>
* <https://www.linkedin.com/in/ardeshir>
* <https://sepahsalar.substack.com/>
* [LinkTree @Sepahsalar](https://linktr.ee/Sepahsalar)
* [Univrs MetaLabel](https://univrs.metalabel.com)
