Some ideas:
1. You could hack the worker to process all queues, then you could have only one worker (?)
2. Stop the worker, modify Koha::BackgroundJob->enqueue to call ->process (not with $self, you will need to refetch the job)
3. You can remove the "use" statements from plack.psgi to reduce plack's memory footprint (but will be slower then)
4. Investigate why the worker is now taking 150M while it was 100 after 28413
5. Care about my bugs when I am working on memory footprint, so that I don't have the feeling to do something nobody cares about... 28410 ;)

Le lun. 23 oct. 2023 à 21:57, Philippe Blouin via Koha-devel <koha-devel@lists.koha-community.org> a écrit :

Howdy!

I'm trying to run a server with MANY koha instances (for educational purposes), but although the usage is very small, the resources required just make everything explode.

background_jobs_worker.pl for instance uses 170M per instance, and plack uses 200M without anything being loaded.

Any suggestion how this could be hacked (locally) to allow for 200 koha instances on a machine without requiring 100G of memory ?  The object model seems at fault here, but I see no way to go around "use Koha::BackgroundJobs;" at the top of the script.

Thanks!

--
Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blouin@inLibro.com

inLibro | pour esprit libre | www.inLibro.com
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/