Server-side hitch warnings, high player ping and low client FPS can indicate different problems. Moving to a plan with more RAM will not necessarily fix a faulty script, oversized map or network issue.
This guide uses measurements to distinguish these issues. Choose a plan using profiles captured under load, memory usage, database size and content size together. There is no universal resource requirement that can be calculated from player count for every RP city.
1. First distinguish the symptoms
| Symptom | What to measure |
|---|---|
| Hitch warning in the server console | Server-side script execution and host load. |
| Alacsony FPS egy adott helyen | Client-side resources, maps, vehicles and graphics load. |
| High ping or dropped connections | The player's network, route and server connection. |
| Slow character or inventory operations | The database, queries and affected script. |
| Gradual deterioration after startup | Memory growth, background tasks and load that changes over time. |
2. Capture a profile while the problem occurs
The profiler works on both server and client. Profiles captured in the server console help diagnose server-side issues; measurements from the client's F8 console show client load. The 500 captured frames are an initial sample, not 500 seconds.
- Record where the error occurred and during which action.
- Capture a sample in the affected environment's console and verify that recording completes.
- Open the profile; server-side profiling may require opening the supplied link in a separate browser.
- Look for long-running tasks at the affected time, then inspect the resource's code and log.
profiler record 500
profiler status
profiler view3. What RAM, CPU and storage reveal
- Assess process memory usage alongside the host's condition when investigating RAM. More RAM does not automatically speed up an inefficient loop.
- Inspect the most time-consuming tasks in the profile alongside aggregate CPU usage. The vCPU count alone is not a measure of processor speed.
- Inspect slow database queries and connection handling too; players can experience these as increased latency.
- Allow disk space for logs, backups and growing content. Script optimisation will not necessarily solve a full disk.
4. Measure one change at a time
- Capture a baseline profile and record the test activity.
- Change a resource, query or content on a test copy.
- Measure again with the same activity and verify that functionality remains correct.
- If measurements show a sustained capacity shortfall, discuss the required upgrade. For script or content problems, fix the underlying cause first.
