Network bandwidth

# Network Bandwidth Considerations for MediaWiki 1.40

This article details the network bandwidth requirements and configuration considerations for a MediaWiki 1.40 installation. Proper network configuration is crucial for a responsive and scalable wiki experience. Insufficient bandwidth can lead to slow page loads, editing conflicts, and an overall poor user experience. This tutorial is aimed at newcomers to MediaWiki server administration.

Understanding Bandwidth Requirements

The bandwidth required for your MediaWiki installation depends heavily on several factors:

• Number of Users: More concurrent users mean greater bandwidth demand.
• Page Complexity: Pages with many images, templates, and external links consume more bandwidth.
• Traffic Patterns: Read-heavy wikis (mostly viewing) require less upload bandwidth than wikis with frequent edits and uploads.
• File Uploads: Allowing users to upload files (images, documents, etc.) significantly increases bandwidth needs, especially upload capacity.
• Caching: Effective caching (see Caching below) reduces the load on the server and network.
• Extensions: Some Extensions may increase bandwidth usage. Review their documentation.

Baseline Bandwidth Recommendations

The following table provides baseline bandwidth recommendations based on wiki size and user activity. These are estimates and may need adjustment based on your specific circumstances.

Wiki Size (Pages)	Concurrent Users (Estimate)	Recommended Download Bandwidth (Mbps)	Recommended Upload Bandwidth (Mbps)
Small ( < 1,000)	1-10	5	1
Medium (1,000 - 10,000)	10-50	20	5
Large (10,000+)	50+	50+	10+

It's always better to overestimate your bandwidth needs. Consider potential growth and peak usage times. Monitor your server's network usage regularly using tools like `iftop` or `nload` on Linux systems. See Server Monitoring for additional details.

Network Components & Configuration

Several network components influence MediaWiki performance.

• Network Interface Card (NIC): Ensure your server has a Gigabit Ethernet NIC (1000 Mbps) or faster.
• Switch: Use a high-quality network switch with sufficient backplane capacity to handle the expected traffic. Avoid bottlenecks.
• Router/Firewall: Configure your router/firewall to allow inbound and outbound traffic on ports 80 (HTTP) and 443 (HTTPS). See Security Configuration for details.
• Internet Service Provider (ISP): Choose an ISP that can provide the required bandwidth and a reliable connection.

Here's a table detailing typical NIC specifications:

NIC Specification	Value
Standard	Gigabit Ethernet (IEEE 802.3ab)	Data Transfer Rate	1000 Mbps (Full-Duplex)	Connector Type	RJ-45	Bus Interface	PCI-e

Optimizing Network Performance

Several techniques can improve network performance:

• Caching: Implement caching at various levels:
* Browser Caching: Configure your web server (e.g., Apache, Nginx) to set appropriate cache headers. * Server-Side Caching: Utilize a caching system like Varnish or Memcached to cache frequently accessed data. * Opcode Caching: Use an opcode cache (e.g., APCu, OPcache) for PHP to reduce PHP execution time.
• Compression: Enable Gzip compression in your web server to reduce the size of transferred data.
• Content Delivery Network (CDN): For globally distributed users, consider using a CDN to cache content closer to your audience. See CDN Integration.
• Database Optimization: A well-optimized Database reduces the load on the server and network.
• Image Optimization: Optimize images for web use (e.g., using tools like ImageMagick) to reduce their file size. See Image Handling.

Here's a table outlining common web server compression settings:

Web Server	Compression Method	Configuration
Apache	Gzip	`mod_deflate` module enabled in `httpd.conf`
Nginx	Gzip	`gzip on;` in `nginx.conf`

Monitoring Network Usage

Regularly monitoring network usage is essential for identifying potential bottlenecks and ensuring optimal performance. Tools like `iftop`, `nload`, and `tcpdump` can provide valuable insights into network traffic patterns. Your ISP may also provide bandwidth usage reports. Review Log Files for additional information.

Related Pages

• Server Hardware
• Server Monitoring
• Security Configuration
• Database Optimization
• Caching
• Extensions
• CDN Integration
• Image Handling
• Log Files
• Apache Configuration
• Nginx Configuration
• PHP Configuration
• Troubleshooting Performance Issues
• Load Balancing
• Disaster Recovery

Category:Server Hardware

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.* ⚠️