https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15262 --- Comment #8 from David Cook <dcook@prosentient.com.au> --- (In reply to Mirko Tietgen from comment #6)
(13:52:14) tcohen: so, put search results in Koha::MetadataRecord object (13:52:42) tcohen: and pass them through a pipe of Koha::Filter-s using the Koha::RecordProcessor thing (13:53:09) tcohen: that's from a perspective in which we re-organize the code (13:53:29) tcohen: and start abstracting things a bit for a future multi-metadata schema support ... (13:55:58) tcohen: if you think about it, we are serializing/deserializing things more than 3 times
Exactly. We're doing too much work processing search results. We need to streamline this process to avoid repeated handling, unnecessary lookups, etc. Besides getting performance improvements, we'll also gain some future-proofing by abstracting away from MARC based search result processing. I'd argue that we should be retrieving the bare minimum from Zebra and then doing the minimal amount of transforming possible. Failing that, if we have to fetch whole MARC records from Zebra, let's set up an optimized pipeline. I reckon that there's no *technical* reason that search shouldn't be fast in Koha. -- You are receiving this mail because: You are watching all bug changes.