I adjusted the scheduled task to only run once a week saturdays at 15:00 and it takes almost 2 hours until cpu/ram goes down again - it is as bad as other services running on the Pi are choked. I guess that something more than just downloading is happening, as that should not be cpu/ram intense.
Is there something I could do to limit the ressources that tmdb trailer is requesting?
Here is a Grafana snapshot of cpu and ram usage when the scraping is running.
I have enabled 5 channels (movie extras is not selected) with max 5 trailers. Plugin is version 12.0.0.0
I'm not completely sure what the libraries download process is like, but it probably transcodes the file. As of right now there isn't anything that can be done to combat this, sorry.
I adjusted the scheduled task to only run once a week saturdays at 15:00 and it takes almost 2 hours until cpu/ram goes down again - it is as bad as other services running on the Pi are choked. I guess that something more than just downloading is happening, as that should not be cpu/ram intense.
Is there something I could do to limit the ressources that tmdb trailer is requesting?
Here is a Grafana snapshot of cpu and ram usage when the scraping is running. I have enabled 5 channels (movie extras is not selected) with max 5 trailers. Plugin is version 12.0.0.0