https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20664
--- Comment #53 from David Cook <[email protected]> --- (In reply to Ere Maijala from comment #52) > Caching during a batch operation would be useful, but it's harder to do > without messing the architecture. And there's still a chance that something > hickups during a batch process and automatic reconnection doesn't kick in > for the cached statement. In any case the performance benefit from caching > the statements, while measurable and significant, isn't dramatic. Yeah, it would certainly require messing with the existing architecture, and I can understand not doing that. If something did hiccup during a batch process and automatic reconnection didn't kick in, then we'd trap and report the error, which doesn't seem like the end of the world to me. But no worries. That's interesting that it's not dramatic. I've seen dramatic performance benefits on other projects, although perhaps that was for more complex queries and higher volumes of data where fractions of seconds can add up dramatically. In any case, you don't have to justify it to me. I'm just curious. Thanks for explaining your thought process to me :). -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
