I'm using Tdarr 2.27.02 on my Synology DS923+ NAS and using this integration to monitor the instance. After upgrading to 1.18 this past saturday I've noticed a constant 15%-20% CPU usage and a gradual increase in memory usage of the NAS, even when Tdarr is idle.
The following are Home Assistant graphs of my DS923+ of the past 10 days. Green are periods when Tdarr was paused, red when the NAS was helping transcoding. The black bar denotes the upgrade from 1.17 to 1.18
As you can see, with 1.17 CPU usage when Tdarr is idle is pretty much 0%, and around 50% when Tdarr is transcoding. Memory usage is also stable.
After the update to 1.18, CPU usage is 15%-20% higher than before, and memory usage is gradually increasing. The sharp dropoff at the end is because I restarted my Tdarr container, only to observer the same behavior again.
I don't know if it's because of the new library code, the new api key authorization, or one of the other commits yet.
I'm using Tdarr 2.27.02 on my Synology DS923+ NAS and using this integration to monitor the instance. After upgrading to 1.18 this past saturday I've noticed a constant 15%-20% CPU usage and a gradual increase in memory usage of the NAS, even when Tdarr is idle.
The following are Home Assistant graphs of my DS923+ of the past 10 days. Green are periods when Tdarr was paused, red when the NAS was helping transcoding. The black bar denotes the upgrade from 1.17 to 1.18
As you can see, with 1.17 CPU usage when Tdarr is idle is pretty much 0%, and around 50% when Tdarr is transcoding. Memory usage is also stable.
After the update to 1.18, CPU usage is 15%-20% higher than before, and memory usage is gradually increasing. The sharp dropoff at the end is because I restarted my Tdarr container, only to observer the same behavior again.
I don't know if it's because of the new library code, the new api key authorization, or one of the other commits yet.