CPU Usage

[IllNate]

I was running fermentrack on a rpi4 and loved it. But I was also using the pi to run a weather station and pihole. I was having trouble with it freezing up and ended up uninstalling fermentrack, which resolved the issue, but I've missed it dearly and have recently installed it in a docker container on my unraid server. Works great, but I'm seeing 25% CPU usage. For comparisson, I have another container running shinobi which records my CTV cameras (2@1440p) feeds 24hrs a day, and this only takes up 10% CPU. Thinking back to the rpi4, I seem to recall that it also hogged an entire cpu thread. Has anyone else noticed this?

[lbussy]

Doesn't seem right:

top - 16:09:47 up 5 days, 44 min,  3 users,  load average: 0.11, 0.03, 0.01
Tasks: 145 total,   2 running, 143 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  0.3 sy,  0.0 ni, 99.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   1002.8 total,    111.7 free,    393.3 used,    497.7 buff/cache
MiB Swap:   1075.0 total,   1052.0 free,     23.0 used.    443.8 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 1678 statd     20   0   47124  19844  10180 R   1.3   1.9 101:09.81 python
  450 root      20   0  978096  33504   9024 S   0.3   3.3   8:27.30 dockerd
 1676 statd     20   0  120508  52828  13492 S   0.3   5.1   9:32.67 python
12821 root      20   0       0      0      0 I   0.3   0.0   0:05.65 kworker/0+
28969 pi        20   0   12436   4576   3764 S   0.3   0.4   0:00.01 sshd
    1 root      20   0   34532   6940   5228 S   0.0   0.7   0:03.24 systemd
    2 root      20   0       0      0      0 S   0.0   0.0   0:00.02 kthreadd

[IllNate]

I see the problem on the docker container, it's creating an infinite log of this:
Jul 19 2021 22:29:41 Refreshing dbConfig
Jul 19 2021 22:29:41 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit

[IllNate]

After restarting the docker container, it stopped doing this. I had a power outage yesterday, so perhaps there's a lockout or something that didn't get released. CPU usage still spiked to 25%, but seems like only once per minute now, which is acceptable.