FAQ
FAQ: Server Configuration for Newcomers
Welcome to the server configuration FAQ
What hardware powers the wiki?
Our wiki runs on a dedicated server cluster to ensure optimal performance and reliability. Here's a breakdown of the primary server specifications:
| Component | Specification |
|---|---|
| CPU | Dual Intel Xeon Gold 6248R @ 3.00GHz |
| RAM | 256 GB DDR4 ECC Registered |
| Storage (Wiki Data) | 4 x 960GB NVMe SSD in RAID 10 |
| Storage (Backups) | 24TB SAS HDD in RAID 6 |
| Network Interface | 10 Gigabit Ethernet |
| Operating System | Ubuntu Server 22.04 LTS |
This configuration allows for high read/write speeds, ample memory for caching, and robust data protection. Regular hardware health checks are performed by the sysadmins to maintain stability.
What software is used?
The wiki's functionality relies on a combination of software components. Below is a summary of the core software stack.
| Software | Version | Purpose |
|---|---|---|
| MediaWiki | 1.40.0 | The wiki engine itself. See MediaWiki Core for more details. |
| PHP | 8.1 | Server-side scripting language. See PHP Configuration for details. |
| MariaDB | 10.6 | Database management system. See Database Maintenance for more information. |
| Apache | 2.4 | Web server. See Apache Web Server for configuration. |
| Redis | 6.2 | In-memory data store for caching. See Redis Caching for details. |
| Memcached | 1.6 | Another in-memory data store for caching (used in conjunction with Redis). See Memcached Usage |
We regularly update these components to benefit from security patches and performance improvements. Always check the Change Log before making changes to your user preferences after an update.
Database Details
The MariaDB database is crucial to the wiki's operation. Here's a detailed look at its configuration:
| Parameter | Value |
|---|---|
| Database Name | mw_wiki |
| Database User | mw_user |
| Maximum Connection Pool Size | 200 |
| InnoDB Buffer Pool Size | 64GB |
| Character Set | utf8mb4 |
| Collation | utf8mb4_unicode_ci |
Database backups are performed nightly and stored offsite. For information on database schema modifications, please consult the Database Schema documentation. Direct access to the database is restricted to authorized personnel for security reasons. If you suspect a Database Error, contact a sysadmin immediately.
Caching Configuration
Caching is essential for maintaining fast page load times. We utilize both Redis and Memcached.
- **Redis:** Used for caching complex queries, API results, and session data. It is configured with a maximum memory limit of 128GB. See Cache Invalidation for details on how to clear the cache.
- **Memcached:** Primarily used for caching frequently accessed fragments of content, reducing the load on the database. It has a maximum memory limit of 64GB.
- **Firewall:** A robust firewall protects the server from unauthorized access. See Firewall Rules for details.
- **Regular Security Audits:** We conduct regular security audits to identify and address potential vulnerabilities.
- **User Account Management:** Strict user account management policies are in place to prevent unauthorized access. See User Rights Management for details.
- **Software Updates:** We promptly apply security updates to all software components.
- **SSL/TLS Encryption:** All communication with the wiki is encrypted using SSL/TLS.
- **Slow Page Load Times:** Check the Performance Monitoring dashboard for potential bottlenecks. Possible causes include high database load, insufficient caching, or network congestion.
- **Database Errors:** Report any database errors to the Help Desk.
- **Wiki Downtime:** Check the Status Page for any planned or unplanned downtime.
- **Edit Conflicts:** See Dealing with Edit Conflicts for guidance on resolving edit conflicts.
- MediaWiki Installation
- Server Administration
- Troubleshooting Guide
- Contacting Support
- System Logs
- Telegram: @powervps Servers at a discounted price
These caches are automatically managed by the wiki software. Manual intervention is rarely necessary, but understanding their role is helpful for troubleshooting performance issues.
Security Considerations
We take security very seriously. Key security measures include:
Common Issues and Troubleshooting
Further Resources
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 configurationNeed Assistance?
⚠️ *Note: All benchmark scores are approximate and may vary based on configuration. Server availability subject to stock.* ⚠️