satisfactory-server: Server RAM Usage and Client Connection Timeout

Describe the Bug When i try joining the game, the server ram jumps from ~2GB to ~7GB (It used less than 5gb earlier) The server gives a lot of errors like

[2022.09.20-23.25.55:491][784]LogNavigationDirtyArea: Warning: Skipping dirty area creation because of empty bounds (object: FoliageInstancedStaticMeshComponent /Game/FactoryGame/Map/GameLevel01/Tile_X5_Y1.Tile_X5_Y1:PersistentLevel.InstancedFoliageActor_0.FoliageInstancedStaticMeshComponent_283)

The client gives a timeout error while those errors are happening. image

Your Runtime Command or Docker Compose File Started it with the command provided in this repo to rule out some things

docker run -d --name=satisfactory-server -h satisfactory-server -e MAXPLAYERS=4 -e PGID=1000 -e PUID=1000 -e STEAMBETA=false -v /path/to/config:/config -p 7777:7777/udp -p 15000:15000/udp -p 15777:15777/udp wolveix/satisfactory-server:latest

System Specs (please complete the following information):

===== START ISSUE REPORT =====
OS:  Linux ubuntu 5.4.0-125-generic #141-Ubuntu SMP Wed Aug 10 13:42:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
CPU: Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
RAM: 10GB/11GB
HDD: 33GB/109GB (32% used)
===== END ISSUE REPORT =====

Additional Context Entire server log

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 58 (10 by maintainers)

Most upvoted comments

I’m going to re-open this because people keep opening new issues. For anyone new that ends up here, this is a known bug with the game server. Please read through this issue, as well as #144. You can see the bug report here:

https://questions.satisfactorygame.com/post/632d2441ca608e080351fb69

Thanks 😃

Keep in mind that most timers in Satisfactory are set for 30 seconds, that’s also what the error tells you in the client, the connection timed out. Judging by your video, it just seems like your server isn’t fast enough to load everything within that time window, the server does not send info to the client to keep alive, so the client disconnects as it didn’t receive data for 30 seconds. This again explains why the second time it does work, because the server finished loading the map in the meantime.

Interesting, has that changed in the update 6? because i didn’t had any issues earlier on, it was just turning on the container, waiting for it to load the world (that now doesn’t do on startup) and just play without any issues.

Knowing that i might do a last test and move it to a Ryzen 9 3900X with gen4 disks and see how it does there

I just watched the video, what instantly gets my attention is that the process of starting up the server and then the process of actually loading the map when you connect is taking absolute ages.

I just double checked my times to verify:

  • Starting the server takes 12 seconds to complete
  • First player connecting to fresh server takes 20 seconds to complete.

Keep in mind that most timers in Satisfactory are set for 30 seconds, that’s also what the error tells you in the client, the connection timed out. Judging by your video, it just seems like your server isn’t fast enough to load everything within that time window, the server does not send info to the client to keep alive, so the client disconnects as it didn’t receive data for 30 seconds. This again explains why the second time it does work, because the server finished loading the map in the meantime.

Your server is the bottleneck and does not have enough performance to be ready within 30 seconds. This makes it all very clear, thanks for the video!

Just a quick visit back to the 11GB RAM if you want to go back to that, your server will use more than that over time, I have never seen it go over 12GB though. But 11GB will fail eventually, even if you get it up and running.

Also, the mention of RAM is as designed, Satisfactory Update 6 dedicated server requires 12GB of RAM.

@MattsBos that’s interesting, I wonder when/why they changed that? The game server (update 4 & 5) needed half of that.

The very first release of Update 6 on the experimental branch came with a considerable rewrite and update (even though it looks like a small update) causing the new requirements. Everyone hopes this will be changed/optimized, but considering the stability it brings and how good the server runs now I think it’s for the better. RAM is cheap, but the simple hobbyist self-hosts on old systems will have some issues with the higher RAM requirement.

Ever since Update 6, the servers I have running are using 11+GB in memory, regardless of connected players or size of the save game. Limiting this manually will cause issues sooner or later. In hibernation the memory usage is around 3GB max. Soon as 1 player connects it will jump to 11GB.

This very update was rolled out to Early Access just a few days ago, I expect a lot more people to find memory problems.

Also, I don’t know why Marko is claiming/seeing such low values and why that would even work on the previous Update 5. As I cannot replicate any of that and don’t see people with that low memory in any of the Discord servers (both Pterodactyl and official Satisfactory) I’m in.

To close off, I don’t understand how you fetched that ingame footage if you can’t connect to your server. Did you just get that from the internet somewhere or did you actually manage to connect to your server eventually, as in your first message you say it doesn’t work, then later you say you got in and then again you say it was impossible.