[UNIFIED] bitwarden/self-host:2023.9.3-beta High CPU usage

[hardwareadictos]

Just updated my APP container to 2023.9.3-beta and Bitwarden now is sitting on +- 50% of VM CPU Usage:

As the base image is a very lightweigh Debian, i cannot check processes. Can someone help me with this?

On my test container all seems fine, only 5 users which are using the service as before. My docker-compose file:

version: "3.8"

services:
  bitwarden:
    container_name: Bitwarden-PRO
    depends_on:
      - db
    env_file:
      - ./env/bw-settings.env
    image: bitwarden/self-host:2023.9.3-beta
    restart: unless-stopped
    ports:
      - "8085:8080"
    volumes:
      - ./bitwarden:/etc/bitwarden

  db:
    container_name: BitwardenDB-PRO
    env_file:
      - ./env/db-settings.env
    image: mariadb:10
    restart: always
    volumes:
      - ./db:/var/lib/mysql

Thanks in advance.

Edit 1: Is even getting worse:

[Aviator7595]

Same for me. Dotnet api.dll and identity.dll are consuming more than 50% of CPU every 10 seconds. To reproduce, it is necessary to login from several devices. Once having this issue, the only solution is to remove the container and run it again from scratch which is very painful. @dev team: please acknowledge the issue so we know it will be fixed some time in the future

[DevSecNinja]

Same issue of high CPU spikes on 2024.5.0-beta. As soon as I spin up Bitwarden, the CPU load rises very fast to load average: 2.93, 0.95, 0.51. Nothing strange in the logs. After deleting the containers, I go back to load average: 0.21, 0.24, 0.27. My config is located here: https://github.com/DevSecNinja/home/blob/main/docker/ansible/templates/compose-modules/bitwarden.yml

[lxne]

Same or similar issue with 2024.10.1-beta and now 2024.10.2-beta.
When I stop the container CPU usage is normal, when I start it, I get high CPU spikes about every 20 seconds.

Resetting the container doesn't change the situation.

Update: Had some other issues with 2024.10.2-beta. I was able to access bitwarden and all my passwords, but I got errors if I tried to change entries or add new ones. Login to web gui didn't work either.
I went back to 2024.9.2-beta which works perfect. No errors, no cpu spikes.

[lxne]

Hm, I think I know where the issues I mentioned in my last post (web gui login, changing entries, possibly cpu usage) came from.

I had two bitwarden containers. The 2024.9.2-beta and a newer one. Off course, I always only started one of both. Running the older one was never a problem, but running the newer ones (tried a view different versions) always gave me issues (strange CPU usage and other errors).

Both containers had the same port settings. And even though the older container was not running, the newer one seems to have had issues with that. After changing the port on the older (not running) container now 2024.10.5 beta works perfect.