[Bug] High CPU idle usage about romm HOT 4 CLOSED

Ok awesome! This would have fixed itself when 3.1 went live and you upgraded, but I'm glad to hear CHOWNing it worked. 👍🏼

from romm.

That's so interesting, I've been investigating high RAM usage (~500MB at idle) for a bit with no luck, but high CPU usage is not something we've observed. I'll have a look when I find a bit of time.

When running htop it seems that the culprit process is python3 scheduler.py

This will be helpful, thank you! Could you also post your docker-compose?

As workaround I've limited the CPU the container can use to 250m of a vCPU instead of the ~750m it was actually using

This is good practice, I do the same with all my containers.

from romm.

I'm not running in Docker but in Kube, but here is the equivalent Docker:

docker run \
 -e DB_HOST=romm-mariadb -e DB_NAME=romm -e DB_USER=romm -e ROMM_AUTH_USERNAME=admin -e IGDB_CLIENT_ID=secret -e IGDB_CLIENT_SECRET=secret -e DB_PASSWD=secret -e ROMM_AUTH_SECRET_KEY=secret -e ROMM_AUTH_PASSWORD=secret \
 --cpus=0.25 \
 rommapp/romm:3.0.3

With volumes and a config.yml mounted. I also have MariaDB in another pod.

I'll happily provide you anything you need. :)

from romm.

Hey!

Yesterday I noticed a scanning bug, and guess I didn't read the Romm logs: I had multiple Redis errors saying it didn't have rights to write, such as this: #812 (comment)

I fixed the error by chowning it, and it seems to have fixed my CPU usage. Ofc I dropped my Prometheus database this morning so I can't verify if the fix matched the CPU usage, but now it's idling well.

Thanks for your help, we may close the issue!

from romm.