Open josuealcalde opened 5 years ago
I think not all libraries have the same coverflow load each time, some update as new books are added, some select random books.
I would suggest optimizing your SQL first as that can help.
Caching would be a possible option to offer, the plugin could have a 'static coverflow' option, saving the report results and allowing the library to update results only when they wish (or via cronjob).
Hi, bravo for this plugin renewal.
Since it uses reports, I think it could use the sql cache used by public reports. Making it easily configurable in reports edition.
Best regards,
Oh I see the cache was implemented then removed : https://github.com/bywatersolutions/koha-plugin-coverflow/commit/4e753c851f70bf03f93307482092c9e967683980
Is there a reason ?
This as a real impact on DB server load.
My Koha Instalation is configured to use memcache and the speed is very good. However, Coverflow takes more than a second to process.
Since the output of coverflow is always the same, ¿would it be posible to cache it?