How to Scale a GTA 6 Server From 32 to 128 Slots
Scaling a GTA server isn't mostly about buying a bigger box. Hardware is the easy part. What kills most scaling efforts are the decisions that were fine at 32, survived at 64 and die at 128.
What breaks first, in order
- Script quality. Every badly written loop that was invisible at 32 players turns into the thing eating 70% of your CPU at 128 players. Profile before scaling up.
- Database connections. By default, connection pools are configured for smaller servers. If you triple your players, you triple your queries, and a host's 50-connection limit will max out before your CPU does.
- Moderation capacity. With 32 players, you can easily get away with one admin. At 128 players, you need three active admins and a tiering system. See our admin team structure guide.
- Disk IO. Logs, chat, positions. Running 128 slots you can produce 2GB of logs daily. Without rotating logs you will fill your disk halfway through the weekend.
- Network budget. You buy 1Gbit unmetered from your host. However, their real egress bandwidth at peak is contested. Get 95th percentile bandwidth numbers from them before you sign a contract.
The 32 to 64 jump
This is the simple one. When scaling a stable 32-slot server up to 64, you normally need to:
- Move up from shared hosting to a VPS or a dedicated slice.
- Increase RAM from 8GB to 16GB.
- Stay at your current CPU level, as long as it's Ryzen 9 class or equivalent.
- Profile your three heaviest scripts at the new player count.
Total cost delta: approximately $15-$30 a month. Expect to be solidly at 64 within a week.
The 64 to 128 jump
This is usually where communities stall. It's not due to hardware limitations, it's because the operational model has to shift.
- You will require your own dedicated hardware now, not a shared node. Noisy neighbours will kill tick rate at 128 slots.
- RAM: Minimum of 32GB, 64GB if you run many database-backed jobs.
- CPU: Ryzen 9 7900X or higher (must have locked boost clocks).
- Storage: Must be NVMe. SATA SSDs will bottleneck your logs.
- Database: Put it on a separate machine, or at least a separate container. Tune MariaDB to handle 200 concurrent connections.
- Admin team: Minimum of three staff online during peak hours, at least one 24/7.
Cost delta from 64 to 128: about $80-$150 per month. Expect approximately two weeks of active tuning following the jump before things start to feel stable again.
When not to scale
If you are at 28/32 players, you do not have a scale issue. You have a marketing issue, or your scripts are too slow for players to stay engaged. Scaling at this point will burn money and often attract the wrong players.
Ideally you want to scale when you're hitting your cap in 9 out of 10 peak sessions for at least 3 consecutive weeks. Until you reach this point, focus on performance optimisation.
Related reading
Our hardware requirements page categorises spec tiers by number of players. Our 2026 cost breakdown provides dollar estimates for each tier. See our CPU bottleneck guide for how to triage performance before you scale.
Frequently Asked Questions
When should I upgrade from 32 to 64 slots?
When you regularly reach your 32-slot cap during 9 out of 10 peak periods for 3+ weeks. Anything less and you're scaling to fix the wrong problem.
What breaks first when scaling a GTA server?
Script quality. If you coded a bad loop that hid at 32 players, it will eat up 70% of your CPU when you have 128 logged in. Profile early, before you scale.
How much more does a 128-slot server cost vs 64?
Estimate another $80 to $150/month for a dedicated-class box vs. a VPS. Throw in some more moderation staff, and perhaps a separate database server. Expect to pay 2x to 3x your total 64-slot costs.
