K-Rise Systems

In building out EASYPay in 5.1 there is a need to process many records at one time (during busy days, there are expected to be 50,000 invoices a day). This is requiring a change on the application side to perform queries with the save to db feature on. Running 1 thread at a time, even if it finishes quickly (taking 1 second an invoice), it will take 14 hours to process all the invoices for the day. So with the current plan, it is not a viable solution.

In addition to this, we will need to have multi-threading, which has been in discussion in the past, but we're not sure if it is ready to use.
There was some discussion in turning a property on in a LOOP to create multiple threads, but not sure if that is how it is planned to be used.

We have some tasks created for this and are working on updating them and consolidating them and will put this change on priority.

Task 8668 will address this feature implementation.

Task 8668 was completed and released in a revision.

There is now task 11008 for some follow up fixes to handle the original use case that was brought up in EASYPay