Thank you for reaching out to Microsoft Q&A forum
Based on my research, the root cause in virtually all such cases is not the total number of items, but how SharePoint executes the specific query for that view. When a view uses a non-indexed column in the first filter condition, in sorting/grouping, or displays many expensive column types (especially lookup, Person/Group, Managed Metadata, calculated, or multiple lines of text or multi-valued ones are the worst and cannot be indexed at all), SharePoint must perform full-table scans or costly joins even on lists with just a few thousand items. This explains both the long delays and the intermittent behavior.
In this context, I highly recommend you follow the below instructions as a practice approach for this situation:
1/ Enable Developer Dashboard (on-demand)
$contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$contentService.DeveloperDashboardSettings.DisplayLevel = "OnDemand"
$contentService.Update()
Then reproduce the slow view and click the dashboard icon (top-right) to check the SQL/query times.
2/ Create the required indexes (List Settings → Indexed columns):
- Index all columns used in filtering, sorting, or grouping (max 20 per list).
- Make the most selective indexed column the first filter.
If it still slow, you can consider running SQL Profiler or Extended Events during a slow load to see the exact expensive query and verify the necessary indexes exist in the database.
Link references:
Living Large with Large Lists and Large Libraries
Software boundaries and limits for SharePoint Servers 2016 and 2019
Optimize page performance in SharePoint
Hope my answer will help you, for any further concern, kindly let me know in the comment section.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.