Avorion Dedicated-Server Performance
Avorion load follows simultaneously active sectors more than the raw player count. An alliance spread across many sectors can stress a server while a larger group sharing one area may be lighter.
Practical sizing
| Galaxy stage | Starting RAM | CPU concern |
|---|---|---|
| Early co-op | 4 GB | Fast core for active sectors. |
| Growing alliance | 6 GB | More sectors, production and scripts. |
| Late-game public galaxy | 8 GB+ | Concurrent sectors and mods. |
When lag appears
- Record how many sectors are active and which players are spread out.
- Check CPU and memory during the event.
- Compare vanilla and modded behavior.
- Reduce loaded-sector pressure before shrinking the saved galaxy.
- Back up before changing difficulty, scripts or mod configuration.
A large galaxy is cheap while empty and expensive when many sectors are active. Size for the community’s month-six play pattern, not only launch night.
See the requirements table and Avorion hosting on high-clock nodes.