Summary: | The tool to bulk edit due dates proxy error times out with large data sets | ||
---|---|---|---|
Product: | Koha | Reporter: | Margaret Hade <margaret> |
Component: | Tools | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | jonathan.druart, kyle |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 24846 | ||
Bug Blocks: | |||
Attachments: | Bug 25088: prevent too many datetime operations |
Description
Margaret Hade
2020-04-08 20:37:49 UTC
By linking to the initial bug this will be a little easier to spot! There is not much we can do. On my laptop, after super quick tests, ~1100 checkouts is processed in ~13s I made it down to 12s with small improvements (datetime handling), but it won't bring significant changes. If we want to display before the process, it will be time consuming. With bug 22417 in mind we could imagine bigger batches (background processing). Or we can provide command line script, but I guess we are loosing the idea of an easy tool that can be used by librarians. You could try playing with the Apache timeout value, but that will need a sysop intervention. Created attachment 102610 [details] [review] Bug 25088: prevent too many datetime operations dropping this now to not forget, but it's not super useful. Note for myself: no sure about the removal of $new_hard_due_date->clone in the sub |