SCP:SL Server Optimization
This guide provides comprehensive optimization strategies for your SCP: Secret Laboratory server to ensure smooth gameplay and optimal performance.Performance Baseline
Before optimizing, establish performance baselines:Key Performance Metrics
Key Performance Metrics
| Metric | Good | Acceptable | Poor |
|---|---|---|---|
| Tick Rate | 60 TPS | 50-59 TPS | Below 50 TPS |
| Server FPS | 60+ FPS | 45-60 FPS | Below 45 FPS |
| RAM Usage | Under 2GB | 2-3GB | Over 3GB |
| CPU Usage | Under 40% | 40-70% | Over 70% |
| Network Latency | Under 50ms | 50-100ms | Over 100ms |
Monitor these metrics through your Wasabi Hosting Gamepanel dashboard or server console.
Configuration Optimization
Gameplay Configuration
Optimizeconfig_gameplay.txt for better performance:
Network Optimization
Configure network settings inconfig.txt:
Server Process Optimization
Optimize startup parameters:Parameter Explanations
Parameter Explanations
| Parameter | Purpose | Performance Impact |
|---|---|---|
-nographics | Disables graphics rendering | High - Essential for dedicated servers |
-batchmode | Runs without user interaction | Medium - Reduces overhead |
-high | Sets process priority to high | Medium - Better CPU allocation |
-logFile | Custom log location | Low - Better log management |
-maxplayers 20 | Limits player count | Variable - Scale based on hardware |
System-Level Optimization
Memory Management
CPU Optimization
Distribute load across CPU cores:Plugin Optimization
EXILED Plugin Framework
Optimize EXILED configuration:Plugin Best Practices
Choosing Efficient Plugins
Choosing Efficient Plugins
Performance-Friendly Plugins:
- Well-maintained and regularly updated
- Minimal event subscriptions
- Efficient database queries
- Proper error handling
- Asynchronous operations where possible
- Abandoned or outdated plugins
- Plugins that hook into every game event
- Poorly coded plugins with memory leaks
- Redundant plugins providing similar features
Database Optimization
If using plugins with database functionality:Entity Management
Item and Ragdoll Cleanup
Door and Elevator Optimization
Round Optimization
Efficient Round Settings
Shorter rounds prevent performance degradation from entity buildup and keep the server fresh.
Network and Bandwidth Optimization
Connection Settings
Port Configuration
Performance Monitoring
Logging Configuration
Balance between information and performance:Performance Alerts
Configure alerts for performance issues:Player Count Optimization
Scaling by Player Count
- Small (8-12 players)
- Medium (12-20 players)
- Large (20-30 players)
Anti-Cheat Optimization
Balance security and performance:Advanced Optimization Techniques
Object Pooling
Async Operations
Caching
Hardware Recommendations
Recommended Specifications by Player Count
Recommended Specifications by Player Count
| Player Count | CPU | RAM | Network |
|---|---|---|---|
| 8-12 | 2 cores @ 3.0GHz+ | 2GB | 10 Mbps |
| 12-20 | 4 cores @ 3.5GHz+ | 4GB | 25 Mbps |
| 20-30 | 6 cores @ 4.0GHz+ | 6GB | 50 Mbps |
These are minimum recommendations. More resources will always improve performance.
Optimization Checklist
Use this checklist to optimize your server:- Configure optimal player count for your hardware
- Enable item and ragdoll cleanup
- Set appropriate despawn times
- Configure network compression
- Optimize tick rate based on player count
- Remove unnecessary plugins
- Enable object pooling
- Configure efficient logging
- Set up automatic round restart
- Enable warhead auto-detonation
- Configure database connection pooling (if applicable)
- Set process priority to high
- Monitor performance metrics regularly
- Keep server and plugins updated
Troubleshooting Performance Issues
High CPU Usage
High CPU Usage
Common Causes:
- Too many plugins running intensive operations
- Large player count exceeding server capacity
- Memory leaks in plugins
- Inefficient event handlers
- Reduce max player count
- Disable non-essential plugins
- Lower tick rate to 50 or 45
- Enable more aggressive cleanup
- Update or remove problematic plugins
Memory Leaks
Memory Leaks
Common Causes:
- Poorly coded plugins not releasing objects
- Excessive ragdoll/item accumulation
- Large log files
- Enable automatic cleanup
- Reduce entity spawn rates
- Restart server regularly (daily recommended)
- Update plugins to latest versions
- Enable log rotation and compression
Network Lag
Network Lag
Common Causes:
- Insufficient bandwidth
- DDoS attacks
- Too many simultaneous connections
- Large packet sizes
- Enable network compression
- Implement rate limiting
- Configure anti-DDoS protection (use Firewall Manager)
- Reduce send/receive rates if needed
- Limit connections per IP
Low Tick Rate
Low Tick Rate
Common Causes:
- Server overloaded
- Blocking operations in game thread
- Insufficient CPU resources
- Too many entities
- Reduce player count
- Enable async operations
- Increase cleanup frequency
- Remove CPU-intensive plugins
- Lower visual quality settings
Maintenance Schedule
Regular maintenance ensures optimal performance: Daily:- Monitor performance metrics
- Check error logs
- Verify tick rate stability
- Review plugin performance
- Clean up old logs
- Update critical plugins
- Analyze player feedback
- Full server restart
- Plugin audit (remove unused)
- Configuration review
- Performance benchmark tests
- Server and plugin updates
Performance Testing
Test optimization changes:1
Establish baseline
Record current performance metrics before changes
2
Apply single change
Make one optimization change at a time
3
Monitor for 24 hours
Observe performance over a full day cycle
4
Compare metrics
Compare new metrics to baseline
5
Keep or revert
Keep change if improved, revert if worse

