| Both sides previous revisionPrevious revision | |
| en:dpi:dpi_brief:dpi_requirements [2025/07/01 11:21] – [Table] atereschenko | en:dpi:dpi_brief:dpi_requirements [2025/08/19 15:40] (current) – [Recommended Requirements] elena.krasnobryzh |
|---|
| | 360 | 320 | **SSG-360** | 192 [[https://www.amd.com/en/products/processors/server/epyc/9005-series/amd-epyc-9965.html|AMD 9965]] | 768 | 28x25G, 20x40G, 12x100G | 24000 | 60M pps | | | 360 | 320 | **SSG-360** | 192 [[https://www.amd.com/en/products/processors/server/epyc/9005-series/amd-epyc-9965.html|AMD 9965]] | 768 | 28x25G, 20x40G, 12x100G | 24000 | 60M pps | |
| <note warning>Important when selecting a server:\\ | <note warning>Important when selecting a server:\\ |
| 1. **The Stingray SG uses only one processor** because of the impact on performance of [[https://en.wikipedia.org/wiki/Non-uniform_memory_access| NUMA]] for dual-processor configurations.\\ | - **The Stingray SG uses only one processor** because of the impact on performance of [[https://en.wikipedia.org/wiki/Non-uniform_memory_access| NUMA]] for dual-processor configurations. |
| 2. **When choosing a CPU, it is necessary to take into account the base frequency **, the higher the frequency, the greater the performance.\\ | - **When choosing a CPU, it is necessary to take into account the base frequency **, the higher the frequency, the greater the performance. |
| 3. **It is recommended to take equipment with a reserve of 20-30% of the planned traffic, in order to prevent congestion during DDoS attacks and the possibility of growth in the future.** For a SSG-40 license implement the SSG-60 platform.\\ | - **It is recommended to take equipment with a reserve of 20-30% of the planned traffic, in order to prevent congestion during DDoS attacks and the possibility of growth in the future.** For a SSG-40 license implement the SSG-60 platform. |
| 4. **The use of 100G** interfaces is possible only when the platform is delivered through a partner in order to control the server specification.\\ | - **The use of 100G** interfaces is possible only when the platform is delivered through a partner in order to control the server specification. |
| 5. **Using the option [[en:dpi:dpi_options:opt_shaping|]]** involves additional internal locks, which reduces system performance to 40G of total traffic per vChannel, regardless of the number of cores.\\ | - **Using the [[en:dpi:dpi_options:opt_shaping:shaping_multi|]] option** and/or **[[en:dpi:dpi_options:opt_shaping:shaping_settings]]** entails additional internal locks, which reduces system performance to 40G (when using tbf) and to 20G (when using htb) of total traffic on a vChannel or on a shared channel, regardless of the number of cores. |
| 6. **Every 256 public IP addresses in NAT Pool (/24 subnet) consume 5GB of RAM. /23 = 10GB, /22 = 20GB, /21 = 40GB, /20 = 80GB, /19 = 160GB.** \\ | - **Every 256 public IP addresses in NAT Pool (/24 subnet) consume 5GB of RAM. /23 = 10GB, /22 = 20GB, /21 = 40GB, /20 = 80GB, /19 = 160GB.** |
| 7. Depending on the amount of routing information, **an additional 4-8GB of memory will be required for the router (Soft-Router)**. | - Depending on the amount of routing information, **an additional 4-8GB of memory will be required for the router (Soft-Router)**. |
| </note> | </note> |
| |
