Hi there,

I’m hosting a dedicated server for satisfactory on my homeserver. It has 16 GB of ram which are 30% used WITH the game running and 4 cores which are barely touching 15% usage, also with the game running.

I checked my connection and it is fairly stable, both on lan and wifi otherwise. I switched to lan so I could debug the connection but it seems like a different problem then wifi.

The server is running in a container from this repo: https://github.com/wolveix/satisfactory-server.

My guess would be that I maybe have accidentally limited the server in terms of ram or cpu usage. Will check.

Let me know if anyone else has this issue. Have a good one. :)

  • @[email protected]
    link
    fedilink
    English
    219 hours ago

    Generally tick length messages are purely due to CPU limitations.

    What hardware is this running on?

    • hauiOP
      link
      fedilink
      English
      119 hours ago

      Xeon 4 core, 4 threads, 16 G DDR4 ram, onboard graphics.

      • @[email protected]
        link
        fedilink
        English
        1
        edit-2
        18 hours ago

        Do you know what CPU model it is? Xeon with 4 threads can range from something so old it can barely run most modern software, to a fairly recent CPU that’s much faster.

          • @[email protected]
            link
            fedilink
            English
            1
            edit-2
            17 hours ago

            That’s on the slower end, but I’ve run a satisfactory server on similar hardware before without too many issues.

            Is the storage SSD based?

            Do you have all 4 cores/threads allocated to the server?

            What about all 16GB of RAM? Satisfactory needs a good amount.

            • hauiOP
              link
              fedilink
              English
              16 hours ago

              I’m monitoring the cpu and ram and so far the server isnt utilizing it except short bursts which dont max out anything. i’ll try and optimize the network first and then go for performance. i suppose its a multi stage issue by now. will update on the matter.