Limiting the number of queue'd filebot run instances
Posted: 09 Dec 2022, 13:48
Good day-
I read a thread on the forums about the expected queue behavior when you run multiple instances of filebot with the --log-file parameters.
I'm not sure if I am alone on this method, but I run my torrent client in a docker, so I execute filebot on the host, and I have no event-driven mechanism to execute filebot.
I have cron executing filebot every 5 minutes. This approach has served me well for a long time.
As the size of movies has gone up, filebot is taking longer to finish it's work. The number of filebot instances in queue is adding up. It's never been a problem per se, I give my host machine enough memory, but I'm considering implementing an approach where I check to see how many instances of filebot are running in my wrapper shell script before running another instance, but wanted to check to see if there are other ideas before doing so.
Thank you.
I read a thread on the forums about the expected queue behavior when you run multiple instances of filebot with the --log-file parameters.
I'm not sure if I am alone on this method, but I run my torrent client in a docker, so I execute filebot on the host, and I have no event-driven mechanism to execute filebot.
I have cron executing filebot every 5 minutes. This approach has served me well for a long time.
As the size of movies has gone up, filebot is taking longer to finish it's work. The number of filebot instances in queue is adding up. It's never been a problem per se, I give my host machine enough memory, but I'm considering implementing an approach where I check to see how many instances of filebot are running in my wrapper shell script before running another instance, but wanted to check to see if there are other ideas before doing so.
Thank you.