MongoDB
# MongoDB Server Configuration
This article details the configuration of MongoDB as a backend database for a MediaWiki installation. MongoDB offers a flexible, document-oriented database solution that can scale well with a growing wiki. This guide assumes a basic understanding of server administration and the MediaWiki installation process. It is intended as a tutorial for newcomers to configuring MongoDB with MediaWiki.
== Introduction to MongoDB
MongoDB is a NoSQL database that stores data in flexible, JSON-like documents, meaning it doesn't require a fixed schema. This flexibility is particularly useful for MediaWiki, which can have a constantly evolving data structure due to extensions and customizations. Compared to traditional relational databases like MySQL, MongoDB can offer advantages in scalability and performance for certain workloads. However, setting up and maintaining it requires a different mindset. Consider the trade-offs before choosing MongoDB. A core concept to understand is the Replica Set, which provides redundancy and high availability.
== Prerequisites
Before beginning, ensure you have the following:
- A server running a supported operating system (Linux is highly recommended).
- MongoDB installed and running. Refer to the official MongoDB Documentation for installation instructions specific to your operating system.
- A functional MediaWiki installation (version 1.40 or later).
- PHP with the MongoDB extension installed and enabled. Check your PHP configuration using `php -m` to confirm the extension is loaded.
- Sufficient system resources (CPU, memory, disk space) to accommodate both MediaWiki and MongoDB. See the section on "Resource Requirements" below.
- **Debian/Ubuntu:** `sudo apt-get install php-mongodb`
- **CentOS/RHEL:** `sudo yum install php-mongodb`
- **Other:** Consult the PHP MongoDB Driver Documentation for instructions tailored to your environment.
- **WiredTiger Cache Size:** Controls the amount of memory used for caching data.
- **Journaling:** Enables durable writes by logging changes to disk.
- **Connection Pool Size:** Limits the number of concurrent connections to the database.
- **Authentication:** Enable authentication to prevent unauthorized access.
- **Firewall:** Configure a firewall to restrict access to the MongoDB port (default 27017).
- **Encryption:** Enable encryption at rest and in transit.
- **Regular Backups:** Implement a robust backup strategy to protect your data. Consider using Backup Strategies for MediaWiki.
- **User Permissions:** Grant users only the necessary permissions.
- **Sharding:** Distribute data across multiple MongoDB servers to improve scalability.
- **Read Preference:** Configure read preference to direct read operations to secondary nodes in a replica set, reducing load on the primary node.
- **Indexing:** Create indexes on frequently queried fields to improve query performance. Proper Database Indexing is crucial for speed.
- MongoDB Official Documentation
- PHP MongoDB Driver Documentation
- MediaWiki Extension Installation
- Database Schema
- Web Server Configuration
- Telegram: @powervps Servers at a discounted price
== Installing the PHP MongoDB Extension
The PHP MongoDB extension is crucial for MediaWiki to interact with the database. Installation varies based on your operating system.
After installation, restart your web server (e.g., Apache or Nginx) for the changes to take effect.
== Configuring MediaWiki to use MongoDB
1. **Edit `LocalSettings.php`:** Locate your MediaWiki installation's `LocalSettings.php` file. This file contains the core configuration settings for your wiki.
2. **Database Settings:** Add the following lines to `LocalSettings.php`, replacing the placeholders with your MongoDB connection details:
```php $wgDBtype = 'mongodb'; $wgDBserver = 'localhost'; // Or your MongoDB server address $wgDBname = 'mediawiki'; // The database name you want to use $wgDBuser = 'mediawiki'; // Database username (if authentication is enabled) $wgDBpassword = 'your_password'; // Database password (if authentication is enabled) $wgDBport = 27017; // Default MongoDB port $wgReplicaSet = 'your_replica_set_name'; // Name of your MongoDB replica set (optional) ```
3. **Replica Set Configuration:** If you're using a MongoDB replica set (recommended for production environments), set the `$wgReplicaSet` variable to the name of your replica set. This ensures failover and high availability.
4. **Authentication:** If your MongoDB instance requires authentication, provide the `$wgDBuser` and `$wgDBpassword` accordingly. Ensure the user has the necessary permissions to access and modify the database.
== Resource Requirements
MongoDB's resource needs vary significantly depending on the size of your wiki, the amount of traffic, and the complexity of your data. Here's a general guideline:
| Resource | Minimum | Recommended |
|---|---|---|
| CPU | 2 cores | 4+ cores |
| RAM | 4 GB | 8+ GB |
| Disk Space | 50 GB | 100+ GB (SSD recommended) |
These are estimates. Monitor your server's performance closely and adjust resources as needed. Using Monitoring Tools can provide valuable insights.
== MongoDB Configuration Options
MongoDB offers a wide range of configuration options that can be tuned to optimize performance. Some key options include:
These options can be configured in the MongoDB configuration file (typically `/etc/mongod.conf`). Refer to the MongoDB Configuration Options documentation for a complete list of available options.
== Security Considerations
Securing your MongoDB instance is critical. Consider the following:
== Troubleshooting
Here are some common issues and their solutions:
| Problem | Solution |
|---|---|
| Connection refused | Verify MongoDB is running and accessible from the MediaWiki server. Check firewall rules. |
| PHP MongoDB extension not found | Ensure the PHP MongoDB extension is installed and enabled. Restart your web server. |
| Slow performance | Check MongoDB logs for performance bottlenecks. Optimize queries and indexes. Increase server resources. |
Refer to the MediaWiki troubleshooting page and the MongoDB documentation for further assistance.
== Advanced Configuration
For larger and more complex MediaWiki installations, consider these advanced configurations:
== Additional 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.* ⚠️