ADB Documentation
ADB Documentation
This document details the server configuration for the Application Database Backend (ADB), which supports critical functionality for our wiki. It is intended for new system administrators and developers needing to understand the environment.
Overview
The ADB is responsible for storing and retrieving data related to user accounts, preferences, watchlist data, recent changes, and various other wiki-related information. It’s a crucial component, and its performance directly impacts the overall wiki experience. This documentation covers the hardware specifications, software configuration, and monitoring procedures for the ADB server. Proper configuration and maintenance are essential for ensuring data integrity and optimal performance. Refer to Manual:Configuration for general MediaWiki configuration guidance.
Hardware Specifications
The ADB server utilizes dedicated hardware to ensure sufficient resources. Details are provided below in a table format.
| Component | Specification | Quantity |
|---|---|---|
| CPU | Intel Xeon Gold 6248R (24 cores) | 2 |
| RAM | 256 GB DDR4 ECC Registered | 1 |
| Storage (OS) | 500GB NVMe SSD | 1 |
| Storage (Data) | 4TB SAS 10k RPM HDD (RAID 10) | 8 |
| Network Interface | 10 Gigabit Ethernet | 2 |
| Power Supply | 1000W Redundant | 2 |
Regular monitoring of hardware health is performed using system monitoring tools. Any anomalies should be addressed immediately. See Special:ListUsers for information on user accounts.
Software Configuration
The ADB server runs a dedicated instance of MariaDB. The following table lists the key software components and their versions.
| Software | Version | Notes |
|---|---|---|
| Operating System | CentOS Linux 7 | Hardened security configuration applied |
| Database System | MariaDB 10.5 | Configured for high availability |
| PHP | 7.4 | Used for database connections |
| Web Server | Apache 2.4 | Proxies requests to the ADB server |
| Firewall | Firewalld | Restricts network access |
The `my.cnf` file (MariaDB configuration) is located at `/etc/my.cnf.d/mediawiki.cnf`. Key settings include `innodb_buffer_pool_size` (set to 128GB) and `max_connections` (set to 500). Review Manual:Database for more details on database configuration. Consider Help:Caching to improve database performance.
Database Schema and Maintenance
The MariaDB database schema is automatically managed by MediaWiki. However, regular maintenance is crucial. This includes:
- Backups: Full database backups are performed daily at 03:00 UTC and stored offsite. See Special:Backup for details on backup procedures.
- Optimization: `OPTIMIZE TABLE` is run weekly on all MediaWiki database tables.
- Analysis: `ANALYZE TABLE` is run weekly to update table statistics for the query optimizer.
- Log Rotation: MariaDB error logs are rotated regularly to prevent disk space exhaustion.
- CPU utilization
- Memory usage
- Disk I/O
- Database connection count
- Database query performance
- Disk space utilization
- Telegram: @powervps Servers at a discounted price
The following table outlines the key MediaWiki database tables:
| Table Name | Description |
|---|---|
| user | Stores user account information. |
| watchlist | Stores user watchlists. |
| recentchanges | Logs recent changes to wiki pages. |
| page | Stores page metadata. |
| revision | Stores page content revisions. |
| category | Stores category information. |
Refer to Manual:DBbackup for detailed backup procedures. Always test restore procedures regularly.
Monitoring and Alerting
The ADB server is monitored using Nagios. Key metrics include:
Alerts are configured to notify administrators via email and PagerDuty when thresholds are exceeded. See Help:Monitoring for detailed information on the monitoring system. Investigate Help:Performance issues proactively. If you encounter problems, consult Help:Debugging.
Security Considerations
The ADB server is protected by a firewall and access is restricted to authorized personnel only. Regular security audits are conducted to identify and address potential vulnerabilities. Database credentials are stored securely and are not hardcoded in any application code. See Project:Security for general security guidelines.
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.* ⚠️