https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27267 --- Comment #3 from David Cook <dcook@prosentient.com.au> --- While these ideas are in the name of efficiency and scalability, there is a downside. They are based on the idea that all the relevant Koha instances are collocated on the same server as the Zebra indexing daemon. Another idea would be to have 1 process per Koha instance (with very minimal memory usage) that either polls the database or listens to RabbitMQ and then forks a child process to run rebuild_zebra.pl (or triggers an API call that does the indexing). This idea is probably the most container friendly. (Another indexing optimization would be to have rebuild_zebra.pl do its work on SSD or RAM disk, since it can perform a lot of I/O for temporarily held data which can be really slow. In the past, we've noticed huge speed improvements by having rebuild_zebra.pl work on a RAM disk.) Reference material: Reading https://stackoverflow.com/questions/9733146/tips-for-keeping-perl-memory-usa... led to many interesting thoughts on memory usage in Perl, especially the part about garbage collection not working the way I expected in Perl. -- You are receiving this mail because: You are watching all bug changes.