> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/setup/prerequisites/hardware-requirements.md).

# Hardware requirements

The following table can be used as a summarized view of the hardware requirements for StifleR.

<table><thead><tr><th width="231">Size</th><th width="97">CPU</th><th width="113">Memory</th><th width="137">NIC</th><th>Disk</th></tr></thead><tbody><tr><td>Under 10,000 clients</td><td>4 cores</td><td>8GB</td><td>Virtual / 1GB</td><td>1x SSD for DBs</td></tr><tr><td>10,000 — 20,000 clients</td><td>8 cores</td><td>16GB</td><td>1GB / 10GB</td><td>2x SSD for DBs</td></tr><tr><td>20,000 — 50,000 clients</td><td>16 cores</td><td>32GB</td><td>10GB</td><td>4x SSD for DBs</td></tr><tr><td>50,000 — 100,000 clients</td><td>32 cores</td><td>64GB</td><td>2x10GB</td><td>6x SSD for DBs</td></tr><tr><td>100,000 —  200,000 clients</td><td>48 cores</td><td>256GB</td><td>4x10GB</td><td>8x SSD for DBs</td></tr></tbody></table>

### CPU

StifleR is CPU intensive. Since StifleR does not use that many threads, a higher frequency (GHz) is recommended. We recommend at least a 2.4GHz processor with 8 cores. Don’t forget that most CPU’s must also handle some of the network connectivity management.

### Memory

StifleR writes a lot of historical data to databases, and also maintains in-RAM memory objects. Since each connection and all connection data is stored in RAM a decent allocation of RAM is recommended but 32GB should be plenty for most installations.

### Disk

StifleR saves a lot of information to ESENT databases, especially with the System Resource Tracking features enabled. Fast SSD disks are preferred for housing these databases.

### Network Connectivity

Each client initiates a non-managed SignalR client connection (web sockets) to the server, so if you want 100k clients to connect to a single server you need to beef up the network connectivity.

If you are supporting a large number of clients, you probably want dual or quad 10Gb/s NIC’s for your StifleR server. This will ensure that the NIC’s have enough power to manage the large number of connections.

### Redundancy

Multiple StifleR servers can be configured for larger enterprises so that clients can fail-over to a second server should the primary server become unavailable.

For larger installations we recommend splitting the load across several StifleR servers. For example one server per geographical region.


---

# 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, and the optional `goal` query parameter:

```
GET https://documentation.2pintsoftware.com/stifler/setup/prerequisites/hardware-requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.