https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41921
--- Comment #56 from Katrin Fischer <[email protected]> --- (In reply to David Cook from comment #54) > (In reply to Katrin Fischer from comment #52) > > I am not sure how it helps the load to run as a background job - it's still > > the same query. Can someone explain what difference it actually makes on the > > server side or what the big advantage here is? > > There's a couple advantages that I can think of. > > If you have a big query/long running report, it might take a long time to > run, and if it's synchronous your browser could time out. > > Also, if you do execute a long running report and then try to page through > it, it would likely be slow. Whereas if you're viewing the results, you > could page through them fairly quickly I suspect. > > A pro/con would also be that it captures a moment in time. The pro being > that you could run a report and its results would be fixed, so you could > rely on that report result again and again. The con would be that it would > be stale immediately after running. But that means it won't help with the situation where a long running query creates load on the server. The advantage is storing it, so multiple people might use the results from within Koha. -- 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/
