Eco players on underpowered servers report actions not registering, world state feeling delayed, and random disconnects during busy sessions. Usually the server cannot keep up with the simulation. Here is why Eco is unusually sensitive to this, what Strange Loop Games changed in Update 14.2, and what it takes to fix.
Why Eco is heavier than it looks
Eco is not just tracking players and their positions the way a typical survival game does. It runs a continuous economic and ecological simulation: every plant growing, every animal population changing, every resource being extracted and processed, and the pollution and environmental effects of all of it, all calculated on an ongoing basis whether or not anyone is actively doing something.
Older guides say this simulation runs on a single thread. That changed with Update 14.2 on 8 October 2026: the periodic world simulation (animal populations, plant growth, pollution) and civics updates (law timers, settlement checks) "now run spread out in the background at low priority instead of saturating assigned cpu cores for up to several seconds". The new BackgroundWorkCpuPercent setting in Performance.eco caps the share of processor cores those background jobs may use (default 25; 0 restores the old behaviour). Hotfix 14.2.1 followed on 16 October with world objects that "update in parallel", "reducing occasional server lag spikes on busy worlds".
Per-core speed still matters. Every job has to finish in time, and when a background job falls behind, the server runs it "immediately at full speed" and prints a warning to the server log. A weak CPU still falls behind the simulation under load, even if it looks adequately specced on paper.
What "the server can't keep up" actually looks like
When the simulation falls behind, the practical symptoms players report are exactly the ones that get mistaken for bugs: an action like chopping a tree or placing an item does not register immediately, the world feels like it is catching up rather than responding in real time, and in more severe cases players get disconnected because the server cannot process their session data quickly enough to keep the connection alive.
This gets worse, not better, as a server's economy matures. A fresh server with a handful of players and a small settlement runs the simulation cheaply. A server that has been running for weeks, with dozens of active players, a developed economy, extensive terraforming, and established supply chains, is running a much heavier simulation every tick, even if the number of concurrently online players has not changed.
What actually fixes it
First update the server: 14.2 and 14.2.1 took load off busy worlds. After that, the fix is server hardware with strong per-core clock speed, not just more RAM. A Ryzen 9 class CPU with high boost clocks handles Eco's continuous simulation load meaningfully better than budget hardware or older CPU generations with a similar core count but weaker per-core speed.
RAM still matters, since a large, established economy with a long game history takes more memory to hold in state than a fresh server, but it is not the first thing to check if the symptom is specifically actions lagging or players disconnecting under load. That points at CPU first.
A quick way to tell
If your Eco server feels fine with a handful of players but starts showing delayed actions or disconnects specifically as more players join or as the economy grows over time, that is consistent with the CPU falling behind the simulation, not a network or client issue. If it happens consistently even with very few players online, it is worth checking that the server is actually running on dedicated CPU resources rather than a shared or oversold host, since Eco's constant simulation load exposes CPU contention faster than lighter game servers do.
To see what is slow, set SlowJobLogThresholdMs to 200 and JobSummaryMinutes to 5 in Performance.eco, the values Strange Loop Games recommends "for investigating performance issues". The server then logs every recurring job that takes longer than 200 ms, plus a summary of all recurring jobs every five minutes.
Hosting an Eco server
Our Eco server hosting runs on AMD Ryzen 9 CPUs with NVMe storage and DDoS protection, in tiers from 4 to 12GB across nine regions. If an established world starts to lag, check CPU load before you move up a RAM tier, for the reasons above.
FAQ
Why do actions not register right away on my Eco server? Usually the server's simulation is falling behind. Update the server to 14.2.1 or newer first, then check CPU load per core and the slow job warnings in the server log.
Does adding more RAM fix Eco server lag?
Not on its own. Eco's simulation is CPU-bound, so CPU speed matters more than RAM for this specific symptom. Since Update 14.2 the simulation updates run as background jobs that can use several cores, up to the share set in BackgroundWorkCpuPercent.
Why does my server lag more now than when it was new, with the same player count? A mature economy with more terraforming, more supply chains, and more world history runs a heavier simulation every tick than a fresh server does, independent of how many players are online at once.
What CPU is best for an Eco server? A CPU with strong per-core performance, such as a modern Ryzen 9, handles Eco's continuous simulation better than hardware chosen mainly for core count.
Are random disconnects on Eco always a hosting problem? Not always, but a server that struggles to keep up with its own simulation can fail to process a player's session quickly enough, which shows up to the player as a disconnect.
Sources
Opened on 4 November 2026:
- Strange Loop Games on Steam: Update 14.2 release notes (background simulation jobs,
BackgroundWorkCpuPercent,SlowJobLogThresholdMs,JobSummaryMinutes), Hotfix 14.2.1 release notes (parallel world object updates)