https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38178 Bug ID: 38178 Summary: Report pagination is inefficient Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs@lists.koha-community.org Reporter: cbrannon@cdalibrary.org QA Contact: testopia@bugs.koha-community.org It seems that the pagination for report results might be causing more bloat in time rather than helping in processing. I thought the purpose of paginating the results was to improve processing time, but when I run a hefty report (say, against the statistics table), it takes a long time to process 20 results, and then the same amount of time for each page I switch to. If feels like it is gathering the entire set of results, then only carving out the number of results it is supposed to show. I think pagination is only beneficial if the report is only processing the range of results being shown. Otherwise, it should just show all results. For example, a report of 1000 results being paginated in groups of 20 should, in theory, process in about 1/50th the amount of time it would take to process all 1000 results. But it feels like it is taking the time to process all 1000 results. I get the logistics of this. In order to process pages of all the results, sorted, grouped and ordered properly, the whole result needs to be taken into consideration, then broken down. But with each page change, it has to do this all over again. It seems that when the report is run, the results need to be stored in a way that the paging would refer to the stored results, not re-run the report. I don't think there is a way to run the report for each page, just for that page's section of results. It seems that the report needs to run in its entirety initially, but then we should have a more efficient way of going through the pages of results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.