As same as the above post, using the same report definition in Smart Dispute We have a requirement to display up to 10,000 records in a dashboard work queue. In the production environment, the volume of records is very high, and there is a possibility that the requested limit may increase further in the future.
Last time, we have increased the count to 2,500. From a performance and scalability perspective, is it advisable to increase this further? @mashwani were you able to resolve this issue?
I would still go back to few points mentioned in the prior post. It is not ideal to show 10k records in the UI especially in a work queue module which is expected to be accessed frequently. This will have performance impact even if your SQL is finetuned.
The recommendation would be to follow the Pega defaults in report definition and enable pagination. You can also do sorting in the list so that the task with higher priority is available to the user without any additional action.
In addition to that validate if Get-Next-Work can help to improve the business process.
If it is a real need to increase it to 10k with all application finetuning, i don’t think the community would be able to answer you with a defined number. Rather, it should be derived based on a performance test to know if the application can handle the load with all your concurrent users and with the load of other modules.
@ArulDevan Thank you for the response, We already Sort using - highest urgency , Dispute Amount and case creation date. We will discuss this further with the users and try to explain that increasing the limit to 10k records may not be the best solution from a performance perspective.