https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27783
--- Comment #66 from Tomás Cohen Arazi <[email protected]> --- (In reply to Marcel de Rooy from comment #65) > (In reply to David Cook from comment #64) > > > koha-worker is just a service wrapper around background_jobs_worker.pl. > > koha-worker could be improved to support more permutations. > In QA I would probably have insisted on keeping things consistent. If you > add it in the script, add it in the wrapper too. The idea was to have a mvp that allowed us to move to this workers from the CGI forking vestiges. And my reasoning around koha-worker was that we should have something that worked out of the box (i.e. koha-common.init launching things). While I like the idea of making koha-worker run more than one queue per process, my perception was that sysadmins would rather dockerize the background_job_worker.pl run to split the load accross servers. > > None of my Koha instances are heavy users of background jobs so it hasn't > > been an issue for me, but I think Bywater are running into issues with not > > having enough workers available. > The development here allows you to start workers per queue. But you need > enough cores too obviously. I notice that the parent waits for the child to > finish; if you code that differently you can fork simultaneously (if cores > allow; could be parametrized) reducing the need for the queue > differentiation again. Yeah, we worked around what was already in core by the time this was added. There are bugs filled for: - Setting a max child count (for parallel processing within a queue) - ACKing on receiving the message -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
