This would lead to a performance improvement by simply lowering the number of records that need to be processed. It would be safe to limit the overdues processed to those under X days overdues given that circulation policy often caps fines at a maximum after a number of days.
Created attachment 98806 [details] [review] Bug 24651: Add maxdays option to fines cronjob This patch adds an optional maxdays parameter to the fines.pl cronjob. The new parameter allows system administrators to set a maximum number of days for the job to process overdues. This can improve performance.
Created attachment 98933 [details] [review] Bug 24651: Add maxdays option to fines cronjob This patch adds an optional maxdays parameter to the fines.pl cronjob. The new parameter allows system administrators to set a maximum number of days for the job to process overdues. This can improve performance. Signed-off-by: Sally Healey <sally.healey@cheshiresharedservices.gov.uk>
This has been applied and tested on Cheshire Shared Services production system and they are pleased with the results. Setting the parameter to 6 months has meant that they do not miss any fines in their environment (as all caps will have been reached by this point), but reduced the runtime from 10 hours to 6 minutes (they have a lot of historical checkouts). Sally asked me to add her signoff line for her :)
Created attachment 98938 [details] [review] Bug 24651: Add maxdays option to fines cronjob This patch adds an optional maxdays parameter to the fines.pl cronjob. The new parameter allows system administrators to set a maximum number of days for the job to process overdues. This can improve performance. Signed-off-by: Sally Healey <sally.healey@cheshiresharedservices.gov.uk> Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Nice work everyone! Pushed to master for 20.05
enhancement not backported to 19.11.x