Anaconda
- Anaconda Server Configuration
This article details the configuration of the "Anaconda" server cluster, a critical component of our infrastructure. This documentation is intended for new system administrators and developers who need to understand the server's architecture and relevant settings. Please refer to the Main Page for general information regarding our systems.
Overview
The Anaconda cluster is a high-performance server designed for handling computationally intensive tasks, primarily related to MediaWiki extension development and database replication. It consists of multiple nodes working in parallel, managed by a central orchestration system. This setup provides redundancy and scalability for our core services, ensuring minimal downtime and optimal performance. Understanding the Anaconda configuration is crucial for troubleshooting issues and proposing improvements to the system. See also the Server Farm Overview for a broader context.
Hardware Specifications
The Anaconda cluster utilizes a homogeneous hardware configuration across all nodes. This simplifies management and ensures consistent performance. The following table outlines the key specifications:
| Component | Specification |
|---|---|
| CPU | AMD EPYC 7763 (64 Cores, 128 Threads) |
| RAM | 512 GB DDR4 ECC Registered |
| Storage (OS) | 2 x 960 GB NVMe SSD (RAID 1) |
| Storage (Data) | 8 x 16 TB SAS HDD (RAID 6) |
| Network Interface | 2 x 100 Gbps Ethernet |
| Power Supply | 2 x 1600W Redundant |
These specifications are detailed in the Hardware Inventory document. Regular hardware health checks are performed according to the Maintenance Schedule.
Software Stack
The Anaconda servers run a customized Linux distribution based on CentOS Stream 9. The software stack is carefully selected to maximize performance and stability. Important components include the PHP version used, the MariaDB database setup, and the Apache web server.
| Software | Version |
|---|---|
| Operating System | CentOS Stream 9 |
| Kernel | 5.14.0-284.11.1.el9_2.x86_64 |
| PHP | 8.1.10 |
| MariaDB | 10.6.7 |
| Apache | 2.4.51 |
| Python | 3.9.7 |
This software stack is subject to change as per the Release Management Policy. Please consult the Software Repository for the latest available versions.
Network Configuration
The Anaconda cluster is connected to the internal network via two 100 Gbps Ethernet interfaces, configured in a bonded mode for redundancy and increased bandwidth. A dedicated VLAN is used to isolate the cluster traffic from other network segments. See the Network Topology diagram for more details.
| Interface | IP Address | Subnet Mask | VLAN |
|---|---|---|---|
| eth0 | 192.168.10.10 | 255.255.255.0 | 10 |
| eth1 | 192.168.10.11 | 255.255.255.0 | 10 |
| Loopback | 127.0.0.1 | 255.0.0.0 | N/A |
Firewall rules are configured using firewalld to allow only necessary traffic to and from the cluster. Refer to the Firewall Configuration document for specifics. DNS resolution is handled by our internal DNS servers.
Monitoring and Alerting
The Anaconda cluster is continuously monitored using Prometheus and Grafana. Key metrics such as CPU usage, memory consumption, disk I/O, and network traffic are tracked. Alerts are configured to notify administrators of any anomalies or potential issues. See the Monitoring Dashboard for a real-time view of the cluster's health. The Alerting System documentation details the escalation procedures.
Security Considerations
Security is paramount. Anaconda servers are hardened according to our Security Guidelines. Regular security audits are conducted and vulnerabilities are promptly addressed. Access to the servers is restricted to authorized personnel only, using SSH key authentication. All data is encrypted at rest and in transit.
Further Information
- Disaster Recovery Plan
- Backup Procedures
- Troubleshooting Guide
- Contact Information
- Server Access Request Form
Intel-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Core i7-6700K/7700 Server | 64 GB DDR4, NVMe SSD 2 x 512 GB | CPU Benchmark: 8046 |
| Core i7-8700 Server | 64 GB DDR4, NVMe SSD 2x1 TB | CPU Benchmark: 13124 |
| Core i9-9900K Server | 128 GB DDR4, NVMe SSD 2 x 1 TB | CPU Benchmark: 49969 |
| Core i9-13900 Server (64GB) | 64 GB RAM, 2x2 TB NVMe SSD | |
| Core i9-13900 Server (128GB) | 128 GB RAM, 2x2 TB NVMe SSD | |
| Core i5-13500 Server (64GB) | 64 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Server (128GB) | 128 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Workstation | 64 GB DDR5 RAM, 2 NVMe SSD, NVIDIA RTX 4000 |
AMD-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Ryzen 5 3600 Server | 64 GB RAM, 2x480 GB NVMe | CPU Benchmark: 17849 |
| Ryzen 7 7700 Server | 64 GB DDR5 RAM, 2x1 TB NVMe | CPU Benchmark: 35224 |
| Ryzen 9 5950X Server | 128 GB RAM, 2x4 TB NVMe | CPU Benchmark: 46045 |
| Ryzen 9 7950X Server | 128 GB DDR5 ECC, 2x2 TB NVMe | CPU Benchmark: 63561 |
| EPYC 7502P Server (128GB/1TB) | 128 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/2TB) | 128 GB RAM, 2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/4TB) | 128 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/1TB) | 256 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/4TB) | 256 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 9454P Server | 256 GB RAM, 2x2 TB NVMe |
Order Your Dedicated Server
Configure and order your ideal server configuration
Need Assistance?
- Telegram: @powervps Servers at a discounted price
⚠️ *Note: All benchmark scores are approximate and may vary based on configuration. Server availability subject to stock.* ⚠️