https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30465
--- Comment #6 from David Cook <[email protected]> --- (In reply to Jonathan Druart from comment #3) > (In reply to David Cook from comment #2) > > I'm not sure I'll be much help, as it looks like this is an Elasticsearch > > specific dev? From the Zebra side I think we'd actually get worse > > performance with this change. > > Why, can you detail please? If I understand correctly, this change would mean that the zebraqueue would only be added to after all the updates are processed, right? At the moment, the zebraqueue is added to with each change, which means the koha-indexer can start processing them ASAP. In theory, this change could make it slower to get records indexed into Zebra. However, if we're passing record IDs through RabbitMQ to a worker to index records in Elasticsearch, I think it could make sense to defer the indexing, so that the background worker can fetch X biblios from the database with 1 DB call before sending them to Elasticsearch. Anyway, I don't think it really matters, so feel free to ignore me hehe. -- 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/
