Update for v1.0 #23
Update for v1.0 #23
Conversation
| const server = new ec2.Instance(this, `${prefix}Server`, { | ||
| // 2 vCPU, 8 GB RAM should be enough for most factories | ||
| instanceType: new ec2.InstanceType("m5a.large"), | ||
| instanceType: new ec2.InstanceType("m6a.xlarge"), |
There was a problem hiding this comment.
This looks like it's doubling the cost of this hourly rate of running. Just a note to point out if this is considered. I believe the original calcs were looking at total cost for a 24 hour uptime were ~$2.06/day.
ec2 instance change: $0.09 -> $0.17 per hour.
I know it's 2->4 vCPUs and 8gb more memory but was there a noticeable difference when playing? Or maybe if someone is looking to have more players on their server?
There was a problem hiding this comment.
I have a +150 hours game with 4 player, and it's barely playable when more than 2 people connect at the same time, with a m7i.xlarge instance (4gb CPU / 16GB RAM).
I'm currently running experiment with an R7i instance (memory optimized, 32GB RAM) and I'm planning to run a test with a C7i instance (compute optimized, even though the aws website state they run the same type of processors)
I will report what I'm observing
There was a problem hiding this comment.
After playing ~10 hours with my R7i instance, I can say that it's a strong improvement.
I have only a few remaining lags, it mostly append when I go to a new zone moving too fast, make it hard for the server to load everything. Once the zone is loaded, everything is fine.
Looks like the game rely heavily on RAM, it would make sense as there are a lot of object put in cache.
Did not have the occasion to test it with multiple people on server yet, but I believe it should be fine.
I would recommend using 16GB of RAM until tier 7 or 8, then switch to 32GB of RAM to keep the game playable.
| Environment="LD_LIBRARY_PATH=./linux64" | ||
| ExecStartPre=$STEAM_INSTALL_SCRIPT | ||
| ExecStart=/home/ubuntu/.steam/steamapps/common/SatisfactoryDedicatedServer/FactoryServer.sh | ||
| ExecStart=/home/ubuntu/.steam/SteamApps/common/SatisfactoryDedicatedServer/FactoryServer.sh -ServerQueryPort=15777 -BeaconPort=15000 -Port=7777 -log -unattended |
There was a problem hiding this comment.
Why specifying ServerQueryPort=15777 -BeaconPort=15000, does it bring any improvement ?
The changelog states that everything goes through the 7777 port, and I managed to run a server only without the ServerQueryPort and BeaconPort parameters
There was a problem hiding this comment.
I just copied the options from the (admittedly out-of-date) wiki and removed the -multihome option. Will take a closer look tonight and test without those options
There was a problem hiding this comment.
Explicitly defining the port is no longer needed unless you want to use a port other than the default of 7777.
ServerQueryPort and BeaconPort are deprecated.
6 participants
Includes all changes from:
In addition changes the following to support Satisfactory v1.0:
-multihome)