Satisfactory
"My server is lagging" is one of the most common tickets we get for Satisfactory, and it usually comes with a request to bump the RAM. More RAM is rarely the fix. Most Satisfactory performance problems come down to CPU and a single setting, not memory. This guide breaks down what's actually happening and what to check before assuming you need a bigger plan.
Why TPS Drops Are a CPU Problem, Not a RAM Problem
Satisfactory's factory simulation, belts, machines, fluids, vehicle pathfinding, all of it, runs on a single CPU thread. The server does use multiple threads for networking and other background work, but the core tick that determines how smooth your factory feels is bound to one core. A developer confirmed this directly on Discord back in 2021: the game loop is fundamentally single-threaded, so one core always ends up doing more work than the rest, no matter how many cores the server has available.
This means adding more CPU cores or more RAM to a server won't speed up a factory that's outgrown its clock speed. What actually determines your ceiling is single-core clock speed.
Checking Your TPS
Satisfactory targets 30 ticks per second. There's no built-in TPS counter, but you can check frame timing with the console command stat unit. If frame time is consistently sitting above roughly 33ms, you're dropping below 30 TPS.
Normal, smooth.
Mildly degraded, occasional stutter.
Noticeably laggy, belts move in bursts.
Effectively unplayable.
Factory Changes That Actually Reduce CPU Load
Rubber-Banding and Desync: Check Network Quality First
Rubber-banding, players or items snapping between positions, and general desync are usually mistaken for server lag, but they're really a client-server sync issue, and the culprit is almost always the Network Quality setting.
Network Quality defaults to Low, which reduces how often the server syncs state with clients to save on CPU. That trade-off is exactly what causes rubber-banding. Set Network Quality to Ultra in Server Settings, and make sure every connecting player also sets Network Quality to Ultra on their own client. A mismatch between server and client settings causes the same symptoms.
When a RAM Upgrade Actually Helps
RAM isn't the direct cause of most lag complaints, but it does matter in a few specific situations:
If TPS is dropping and RAM usage isn't near its ceiling, more RAM won't help. That's a CPU and factory complexity problem, covered above.
Other Things Worth Doing
Scheduled restarts: Set a Server Restart Schedule in Server Settings. A daily restart is a reasonable default; heavily built servers may benefit from restarting every 12 hours or so. This is the most effective long-term fix for the gradual memory growth mentioned above.
Autosave interval: If your server stutters on a suspiciously regular cycle, check whether it lines up with your autosave interval. Large factories can see a brief TPS dip while a save writes to disk. Increasing the interval in Server Settings reduces how often that happens, at the cost of losing slightly more progress if the server crashes between saves.
Quick Diagnostic Checklist
If you've worked through all of this and TPS is still dropping, you've likely hit the single-core CPU ceiling for your current factory's complexity, at that point the options are optimizing further, splitting production across multiple servers, or accepting the trade-off of building at that scale.
Still stuck?
Our team is happy to help. Open a ticket through the live chat button in the bottom-right corner of our website, or join our Discord and open a ticket there.
Join our Discord