What are you doing that you need all 10k records? If this is a data sync/migration operation, then 20 seconds seems acceptable. If it’s not a data sync, why do you need so many records?
There are a few things to consider here:
Anything that cannot be fetches in <1 second should not be a blocking action for the user. This means that you either:
* fetch just a few records from oracle, e.g., by providing search expression (as mentioned by connor) or limit the records with offset/limit,
* or you do it in the background: create a microflow that runs once per hour/per day/on user login, that fetches a lot of records and caches them in the mx app database. This way the Mx UI can fetch just a few records from the database.
Hi Romil,
Reading your question and comments on Conner, I think the approach is not the best way to go foward. The fact that you build an application that might give the avarage user a list of 3k records in a dropdown, is asking for trouble in my opinion. In addition, if the business prefer 3000 records in a dropdown instead of a search function (such as Connor mention) you and the business are facing hard times.
So, perhaps you could ask your stakeholderd (or product owner) why they think you need 10k records, put them in a dropdown and do not want to have this pre-filtered by search functionality? Perhaps with their motviation I can help you finding a solution on their request. Just wanting to process 10k records is just a too less info (in my opinion) to find a solution on your perfroamnce issue.
hopes this helps,
Jan