search

mornedhels / enshrouded-server

Enshrouded Dedicated Server with autoupdate (supervisord)
MIT License
124 stars 8 forks source link

High server load messages / low CPU utilization #113

Open LuxKeiwoker opened 6 hours ago

LuxKeiwoker commented 6 hours ago

Is there an existing issue for this?

Used image version

latest - 1d77460

Used docker compose file or docker command

services:
  enshrouded:
    image: mornedhels/enshrouded-server:latest
    container_name: enshrouded
    hostname: enshrouded
    restart: unless-stopped
    stop_grace_period: 90s
    ports:
      - "15637:15637/udp"
    volumes:
      - ./game:/opt/enshrouded
    environment:
      - SERVER_NAME=Enshrouded Server
      - SERVER_PASSWORD=secret
      - UPDATE_CRON=*/30 * * * *
      - PUID=4711
      - PGID=4711

What you expected to see, versus what you actually saw

I'm running this container on a Synology NAS with AMD Ryzen CPU and 6 Cores/12 Threads. As soon as more than one player is connected, the game starts complaining about high server load or even excessive load. While looking into the CPU utilization of the container I see only a utilization of up to 300 %, i.e 3 cores or threads.

The Synology Resource Manager (kind of a taskmanager like in Windows) shows a Cpu utilization of only around 20 %. I've tried many things like redeploying the container, turning on resource restriction, turning it off. Setting the priority of the container to high and even started messing with the docker -cpushares parameter through ssh. Nothing has ever increase CPU utilization.

At this point I suspect somethings off with the container, rather than the host machine or configuration.

Any ideas?

Logs from the container

No response

Zaarrg commented 5 hours ago

+1 Got exactly the same issue. With only 2 players got rubber banding and the high server load message in game. Server has more then enough resources with a i5 13500, 20 threads and 64gb, 1 GBit/s network. Meanwhile the enshrouded server used max 2gb ram with a max load of 300% aswell. No idea if its a docker image issue or enshrouded as i found also a recent reddit post with the same issue.