Identify the workload
Provide the game or application, server OS, plugin count and expected concurrent users. For software sensitive to single-thread performance, compare CPU models rather than core counts alone.
Test from player networks
Test separately by player region and carrier. Record latency, loss and test times during busy and quieter periods. Network Lab can help, but public probes do not replace tests from players’ connections.
Confirm protection needs
Do not choose ordinary dedicated hosting for a workload that requires DDoS protection without checking coverage. Provide protocols, ports and known attack details, and confirm mitigation and null-routing terms.
Before launch
Check the OS, server dependencies and backup plan. Start with a small connection test before increasing load. Submit reinstall and power-operation requests through the client area for manual handling.