Loading

LEX list view performance in Google Chrome

Julkaisupäivä: Oct 13, 2022
Kuvaus
Scrolling performance in Lightning Experience List Views degrades based on the number of rows in the page. For example, when 300 rows are being displayed in the List View, scrolling is somewhat slower, but more so with 500 rows and even more so with 800 rows.

The overwhelming reason for why scrolling gets more expensive with more rows in the table is the time the browser spends recalculating styles - and this is driven by the amount of HTML elements in the page. The number of HTML elements, unsurprisingly, is driven by the number of rows shown - which explains why performance degrades based on the amount of content loaded.

This comes down to how Chrome chooses to manage the HTML elements that have been drawn. We've compared in Firefox as well and have noted that Firefox will remove HTML elements and store them in cache as necessary, and will re-draw them on the page as you scroll up and down through a page that utilizes infinite scrolling. Chrome however does not remove the elements from the page, as you scroll further down through a page the browser will retain an ever growing number of HTML elements. This has been observed not only in Salesforce, but also in Google Drive when scrolling through a large number of documents or images.
Ratkaisu
We do have the following recommendations to mitigate performance impact from how Chrome handles the HTML elements: 

1. Our first recommendation would be to not use a list view to scroll through such a large volume of content. It's hard for a user to find something they're looking for in 500 rows - so let the computer do the work for you. If you know the specific entry you're looking for, use the search bar to find it. If you're looking for a specific type of entry, we recommend that you use filters on the list view to restrict the view to those types of entries.
2. Another alternative is to use a report instead of a list view. Reports use a simpler layout, with far fewer HTML elements per row. In our own testing we've seen that a report with 1,000 records in it was able to scroll much more smoothly than the list view with 1,000 records.
3. For users on PC, you can also try to disable the smooth scrolling setting in Chrome to see if there is improvement. Results may vary, but in our testing this has helped. You will want to put the following in your Chrome browser, and set Smooth Scrolling to Disabled: 

chrome://flags/#smooth-scrolling

4. Another setting that we observed some improvement in performance for as well is threaded scrolling. This setting advises that disabling it can hurt performance, but we noticed in our testing that scrolling seemed to behave a little better in lightning list views with this setting disabled. 

chrome://flags/#disable-threaded-scrolling

If you want to stay with list views, there are also several options for reducing the amount of HTML elements per row in the table: 

1. Reduce the number of columns being displayed. If fewer columns are shown, there are fewer elements per row, and scrolling will be overall faster. We experimented with this by creating a new list view and removed two columns. It's somewhat faster, even with 800 rows being shown in the page.
2. Disable inline editing - if you're not using inline editing. Inline edit creates multiple additional HTML elements per row. Unfortunately, this is an org-level setting, so its effects will be felt broadly within your organization.
3. Lastly, part of the list view performance issues have been found to be associated with a CPU bottleneck - we've tested with various clocked i7 processors and noted that the performance was far worse on a 2.2GHz processor as opposed to 2.6GHz or greater. This option is likely not feasible, but provisioning hardware with a more powerful CPU will greatly improve performance as well.
Knowledge-artikkelin numero

000383739

 
Ladataan
Salesforce Help | Article