Question

Whenever it comes to Views in SharePoint (2013 or above), the documentation offers it as a way to get around limitations (usually 5000 elements).

I currently use CSOM to retrieve data from SharePoint (Office365) lists. (So I only care about Select here). And is really slow, even on small Lists. Or to put it in other words: If Data Storage is Marines, SharePoint-Lists seem to be Private Pyle.

I created Indices and Views to speed up performance but cannot really see any measurable effect. Is there any performance effect at all or is it really just to get around limitations?

Has anyone ever made any measurements to track the performance boost using views and/or indexes in SharePoint-Lists?

(Additional Info):

I use Caml Queries containing only the Fields (and conditions) I need and fire them using listname.GetItems(query)

Was it helpful?

Solution

I think additional overhead of an index and multiple indices don’t give you additional performance gain **

Example

For every defined index, SharePoint stores the index value for every list item in a separate table.

Having a list with let’s say 50000 items means that we have 50000 rows in AllUserData and 50000 additional rows in the NameValuePair table.

So every time you update your list – NameValuePair need to be updated as well.

Licensed under: CC-BY-SA with attribution
Not affiliated with sharepoint.stackexchange
scroll top