Bug 41208 - Log viewer should use an API or limit max results per search
Summary: Log viewer should use an API or limit max results per search
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: 25.05
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-06 16:50 UTC by Kyle M Hall (khall)
Modified: 2025-11-06 16:50 UTC (History)
0 users

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall (khall) 2025-11-06 16:50:44 UTC
Koha's log viewer loads all results at one time into a datatable. Large systems can have potentially hundreds of millions of rows. An unconstrained search can easily use up all the RAM even on systems with dozens of gigbytes of memory.

Koha should either have a limit of the query and encourage users to limit their query further if the full results cannot be displayed, or we should use the API for paginated results.