Profiling Tool
# Profiling Tool - Server Configuration
This article details the configuration and usage of the profiling tool available on our MediaWiki servers. This tool is critical for identifying performance bottlenecks and optimizing server resource allocation. It is aimed at system administrators and developers involved in maintaining and improving MediaWiki performance. Understanding its configuration and output is vital for efficient troubleshooting and scaling.
Overview
The profiling tool leverages a combination of system-level monitoring and application-level tracing to provide a holistic view of server performance. It collects data on CPU usage, memory consumption, disk I/O, network traffic, and database query execution times. This data is then aggregated and presented through a web interface, allowing for easy analysis and identification of problem areas. This tool is distinct from Special:Statistics, which provides aggregate usage data. It’s also different from Manual:How to debug, which focuses on PHP-level debugging.
System Requirements
The profiling tool requires specific system configurations to operate effectively. These are detailed below.
| Component | Requirement |
|---|---|
| Operating System | CentOS 7 or Ubuntu 20.04 LTS |
| CPU | Minimum 4 cores, recommended 8+ cores |
| Memory | Minimum 8 GB RAM, recommended 16+ GB RAM |
| Disk Space | Minimum 50 GB free space for logs and data |
| Database | MySQL 5.7 or MariaDB 10.4 (or compatible) |
| PHP Version | PHP 7.4 or PHP 8.1 |
These requirements ensure sufficient resources for data collection and analysis without significantly impacting the performance of the MediaWiki instance itself. Failure to meet these requirements may result in inaccurate data or tool instability. Consult the Manual:Configuration settings for further details.
Installation and Configuration
The profiling tool is installed as a separate service alongside the MediaWiki installation. The installation process involves downloading the tool's packages, configuring access credentials, and integrating it with the MediaWiki environment. This process is automated through our deployment scripts; however, understanding the underlying configuration is important for troubleshooting.
The primary configuration file, `profiling.conf`, resides in `/etc/profiling/`. This file controls data collection intervals, storage locations, and security settings. Key parameters include:
- `data_retention_period`: Specifies the number of days to retain profiling data.
- `sampling_interval`: Defines the frequency at which data is collected (in seconds).
- `database_credentials`: Contains the username and password for accessing the profiling database.
- `allowed_users`: A list of users authorized to access the profiling web interface.
- **Custom Metrics:** The ability to define and collect custom metrics specific to the MediaWiki environment.
- **Alerting:** Configuration of alerts that trigger when certain metrics exceed predefined thresholds.
- **Integration with Monitoring Systems:** Integration with external monitoring systems such as Monitoring:Nagios or Monitoring:Prometheus.
- Verify that the profiling service is running.
- Check the profiling logs for any errors.
- Ensure that the database credentials in `profiling.conf` are correct.
- Confirm that the allowed users in `profiling.conf` have the necessary permissions.
- Review the Manual:Troubleshooting guide for common issues.
- Telegram: @powervps Servers at a discounted price
It is crucial to secure the `profiling.conf` file with appropriate permissions to prevent unauthorized access. See Help:System administration for more security guidance.
Data Collection and Analysis
Once installed and configured, the profiling tool automatically begins collecting data. The data is stored in a dedicated database, optimized for time-series data. The web interface provides a range of charts and graphs for visualizing the collected data.
| Metric | Description | Analysis Focus |
|---|---|---|
| CPU Usage | Percentage of CPU time consumed by MediaWiki processes. | Identify CPU-bound operations and potential code optimizations. |
| Memory Consumption | Amount of memory used by MediaWiki processes. | Detect memory leaks and optimize memory usage. |
| Disk I/O | Read/write operations performed on the disk. | Identify disk bottlenecks and optimize database queries. |
| Network Traffic | Amount of data transferred over the network. | Analyze network latency and optimize caching strategies. |
| Database Query Time | Execution time of database queries. | Identify slow queries and optimize database schema. |
The tool also provides detailed traces of individual requests, allowing developers to pinpoint the exact lines of code that are causing performance issues. These traces are invaluable for debugging complex problems. Refer to the API:Query debugger for further details on query optimization.
Advanced Configuration
For more advanced users, the profiling tool offers several customization options. These include:
These features allow for a more tailored and proactive approach to performance monitoring.
| Feature | Configuration Location | Description |
|---|---|---|
| Custom Metrics | `/etc/profiling/custom_metrics.conf` | Define new metrics to track based on specific application needs. |
| Alerting Rules | `/etc/profiling/alerting.conf` | Configure alerts based on metric thresholds. |
| External Integration | `/etc/profiling/integration.conf` | Configure integration with external monitoring systems. |
Remember to restart the profiling service after making any changes to the configuration files. The service can be restarted using the command `systemctl restart profiling`. For further support, consult the Help:FAQ or contact the system administration team.
Troubleshooting
If the profiling tool is not functioning correctly, check the following:
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.* ⚠️