How to find the root cause for slow record lists?

Hi Rahul, as per my understanding, Related Actions will be loaded only when you click on Related Action tab/views or record view (if related actions are configured to show on these views).

So when record gets loaded, following activities will performed:

1. Query number of rows as per configured batch size
2. Execute default filter for each one of the rows
3. Load the user filter (does not filter the rows on load)
3. Check for security privileges

In your case, as you are saying that, the db returns the result in 50 ms then I believe you need to have a look on your default filters , because if you are performing some complex logic then it's obvious to decrease the performance.

If default filters are the root cause behind slowness, then I recommend create a view based on these pre filtering conditions to avoid default filters (if possible in your use case)

Hi Rahul Gundu ,

I'm agree with Alok. I just can add that you can also try to check again how you are creating the record list, even if it is a table or feed, check if you are using any expression rule to show any data that could be making slow to display info.

Can you post the expression for your default filter?

How many rows are in the table or view that backs this record? Is the workroom field indexed in any way?

If you query the table or view using that default filter (eg WHERE workroom = 'FF'), how long does it take to run?

Index applied on workroom field.

Total Records 403112 (0.0009 sec)
FF Records 184624 (0.0036 sec)

Ok, and is the list view a grid or a list? If it's a list could you give the expression used for the list view item, alternatively if it's a grid are any expressions used in the field definitions?

No additional rules used in record list definition. I'm just calling 3 fields in record list from table

Is it a list view or a grid view?

list view

Have you tried it as a grid view? Given querying the table with the default filter appears to be fast, that might actually be the issue. Another alternative is to switch to a service backed record - in fact, given the volume of data in the table I'd recommend using a service backed record - but give it a try as a grid view first.

Can you let us know if you have many visible condition on the related actions. This is also a defining factor for the performance as it executes for all records and every time you perform actions on records. given the number of concurrent users in the system this could potentially slow down the the record list.

Also, can you verify when the record list is slow, does same applies to other components in the application, like other process records and overall performance in you application?

You can also check the the DB Log files to identify slow performing queries.

Regards
Suresh G

Can you let us know if you have many visible condition on the related actions. This is also a defining factor for the performance as it executes for all records and every time you perform actions on records. given the number of concurrent users in the system this could potentially slow down the the record list.

Also, can you verify when the record list is slow, does same applies to other components in the application, like other process records and overall performance in you application?

You can also check the the DB Log files to identify slow performing queries.

Regards
Suresh G