https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36239 Bug ID: 36239 Summary: Availability calculation in OPAC Results XSLT is too slow Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs@lists.koha-community.org Reporter: dcook@prosentient.com.au QA Contact: testopia@bugs.koha-community.org buildKohaItemsNamespace is really slow in XSLTParse4Display when there is a record with a large number of items. On one system, we notice a search on the staff interface is 12 seconds whereas it's 1-2 minutes in the OPAC. I'm slowly tweaking things to improve the speed, but one of the big killers is buildKohaItemsNamespace. I think there are many use cases for having a Real Time Availability API endpoint, and this would be one of them. We could have a little loading CSS-driven graphic, send a list of biblionumbers to the endpoint asynchronously, and then render the availability. If we handle the availability through that endpoint (or at least a singular model method), we should be able to make further optimizations to availability calculation as well... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.