# Hardware Sizing

Class 4 Fusion is built using C and on top of sofia-sip stack.  It is extremely efficient so you don't need a lot of hardware power to run a high volume of traffic. 

The size of disk depends on CPS and how many days of CDRs you want to keep in DB and in local disk. As you can push CDRs to Google Cloud, you don't need to keep many CDRs in local disk in raw format.  However, you may want to keep more CDRs in DB for UI query.  

You should estimate about 200 GB of disk space per day of CDR. 

#### 50000 Ports / 10000 CPS

| Component | Spec                                                    |
| --------- | ------------------------------------------------------- |
| Memory    | 128 GB                                                  |
| Disk Size | 2 X 4 TB                                                |
| CPU       | Intel 2x Xeon Silver 4214 - 24 c / 48 t - 2.2 GHz / 3.2 |

####

#### 10000 Ports / 3000 CPS

| Component | Spec                                                    |
| --------- | ------------------------------------------------------- |
| Memory    | 128 GB                                                  |
| Disk Size | 2 X 4 TB                                                |
| CPU       | Intel 2x Xeon E5-2650v3 - 20 c / 40 t - 2.3 GHz / 3 GHz |

#### 5000 Ports / 1000 CPS

| Component | Spec                                                      |
| --------- | --------------------------------------------------------- |
| Memory    | 128 GB                                                    |
| Disk Size | 2 X 4 TB                                                  |
| CPU       | Intel 2x Intel Xeon-E 2274G - 4 c / 8 t - 4 GHz / 4.9 GHz |


---

# Agent Instructions: 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://cookbook.denovolab.com/hardware-sizing.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.