Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:dpi:dpi_components:qoestor:install_and_update:hardware_recommendations [2022/03/24 14:59] – arusnak | en:dpi:dpi_components:qoestor:install_and_update:hardware_recommendations [2025/01/13 13:45] (current) – [Table] elena.krasnobryzh | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== 2 Equipment | + | ====== Equipment |
{{indexmenu_n> | {{indexmenu_n> | ||
- | <note important> | + | <note important> |
- | === Minimum | + | ==== Minimum |
- | + | The component | |
- | For the subsystem, you can use hardware or virtual machines | + | - Processor (CPU) 2.5 GHz - 1 core |
- | - Processor (CPU) 2.5 ГГц | + | |
- RAM - at least 16 GB | - RAM - at least 16 GB | ||
- | - Hard disk drive (SSD is highly | + | - Hard disk (SSD highly |
- | - Operating system - CentOS 7.x, CentOS 8.x, CentOS Stream 8.x, Oracle Linux Server 8.x, AlmaLinux 8.x | + | - Operating system - CentOS 8.x, [[en: |
- | - Network interface (NIC) - at least 1 Gbps | + | - Network interface |
- | <note important> | + | |
- | + | ||
- | == Processor == | + | |
- | + | ||
- | SSE 4.2 instruction set support is required. | + | |
- | + | ||
- | Choose processors with a large number of cores. Clock frequency is less important. For example, 16 cores with 2,600 MHz are better than 8 cores at 3,600 MHz. | + | |
- | + | ||
- | <note important> | + | |
- | + | ||
- | == RAM == | + | |
- | + | ||
- | RAM should be no less than the amount of data requested. | + | |
- | + | ||
- | The more RAM server has, the better performance will be achieved when building reports. | + | |
- | + | ||
- | The more memory, the less disk system is stressing. | + | |
- | + | ||
- | Minimum prerequisites is 16 GB. | + | |
- | + | ||
- | Always disable the swap file. | + | |
- | + | ||
- | == Disk == | + | |
- | + | ||
- | Required disk space is at least 16 GB for every storage day, it's actual value depends on daily traffic. It is estimated that 10 Gbit/s of average daily traffic generates approximately 25 GB of data per hour in the QoE Store. | + | |
- | + | ||
- | If your budget makes you possible to use SSD, use it. Otherwise use HDD. SATA HDDs 7200 RPM will be suitable. | + | |
- | + | ||
- | When using HDD, you can combine them into RAID-10, RAID-5, RAID-6 or RAID-50. | + | |
- | + | ||
- | Most of the data is stored in the ''/ | + | |
- | Temporary data (ipfix dumps) is stored in the ''/ | + | ==== Recommended Requirements for Every 10Gbps Peak Traffic on DPI ==== |
+ | - Processor | ||
+ | - RAM - 64 GB | ||
+ | - Hard disk (SSD highly recommended) - at least 500 GB, see below for storage volume calculation and storage organization recommendations | ||
+ | - Operating system - CentOS 8.x, [[en: | ||
+ | - Network interface card (NIC) - 2x10Gbps. It should | ||
- | For best performance, | + | Example of a QoE server receiving IPFIX from DPI for 100Gbps peak traffic |
+ | Server platform (2U, AMD EPYC 7713 processor with 64 cores, 512 GB RAM, HW RAID Controller, 2 x 960GB SSD RAID1 for OS, 4x3.84TB SSD NVME RAID0 stripe default disks + HDD/SSD RAID50 disks for storage of a specific volume, 2x network adapter 2x25GbE, 2xPSU) | ||
- | === Maintenance advice from Yandex ClickHouse | + | === Storage Volume Calculator Based on Average Traffic Speed === |
+ | It is assumed that the average daily traffic is 60% of the total peak (in+out) traffic. | ||
+ | ==== Detailed Recommendations ==== | ||
+ | | CPU | **One processor** supporting **SSE 4.2** instructions starting from [[http:// | ||
+ | | RAM | At least 16 GB, memory modules must be installed **in all processor channels** on the motherboard. Memory should be no less than the volume of requested data. More memory improves performance when generating reports. More memory also reduces disk load.\\ **Always disable swap file.** | ||
+ | | Disks | To optimize storage costs, several types of disks are used: \\ default — fast disks for data reception and aggregation process, it is recommended to use SSD NVMe in RAID0. \\ hot — disks for storage during periods of higher likelihood of report requests on this data, typically up to 3 months, SSD disks in RAID-10, RAID-5, RAID-6, or RAID-50. \\ cold — slow, large-volume disks for long-term storage, HDD disks in RAID-10, RAID-5, RAID-6, or RAID-50 are recommended. \\ The storage duration for each level is set in the configuration via the GUI. Data migration between disks and data cleanup happens automatically based on the settings. A mechanism for overflow control is also provided to protect the database. The main volume of data is stored in the / | ||
+ | | QoE Cluster (Sharding) | ||
- | You could familiarize yourself with the contents of maintenance advice | + | ==== Tips from Yandex ClickHouse |
+ | You can read Yandex ClickHouse operation tips at [[https:// | ||