Test big data in the SharePoint 2013 list <2>

1. Add 100 query item fields to the test list. The Code is as follows:

2. Insert the test data. Check the format of the item field. The Code is as follows:

3. Insert 10 million data records, which takes the following time (it is not recommended to list [listname]. Items. Add, which will be slow ):

4. Check the list settings. There are 10 million data records and the threshold value is 500, for example:

5. Go to the allitems page and find that the number of query item fields is greater than the limit (8), for example:

6. Modify the maximum number of items (modified to 500), for example:

7. Check the test data when there are 100 item fields, as shown in the following table:

Table 1: page 30, lookup field 50;

View Project count	Lookup field count	Page Turning time
30	50	17 S
		15 s
		15 s
		15 s
		14 s

Table 2: page 100, lookup field 50;

View Project count	Lookup field count	Page Turning time
100	50	42 s
		44 s
		43 s
		42 s
		43 s

Table 3: page 30, lookup field 15;

View Project count	Lookup field count	Page Turning time
30	15	5.09 s
		5.69 s
		5.10 s
		5.52 s
		5.32 s

Table 4: page 100, lookup field 15;

View Project count	Lookup field count	Page Turning time
100	15	13 s
		14 s
		14 s
		14 s
		14 s

Table 5: page 30, lookup field 8 (default value: 8 );

View Project count	Lookup field count	Page Turning time
30	8	3.13 s
		2.82 s
		3.08 s
		3.78 s
		2.94 s

Table 6: page 100, lookup field 8 (default value: 8 );

View Project count	Lookup field count	Page Turning time
100	8	5.35 s
		5.54 s
		7.46 s
		7.80 s
		8.10 s

Table 7: Page 300, lookup field 8 (default value: 8 );

View Project count	Lookup field count	Page Turning time
300	8	16.48 s
		17.13 s
		17.30 s
		17.52 s
		17.59 s

8. Insert 10 million data records and 100 single-line text fields. The insertion time is as follows:

9. Test Data when there are 10 million data records and 100 single-line text fields, as shown in the following table:

Table 8: Page 500, text field 100;

View Project count	Text Field count	Page Turning time
500	100	7.22 s
		6.28 s
		7.10 s
		6.81 s
		5.76 s

Table 9: Page 1 K, text field 100;

When the page size is 1 kb, the page is very slow.

View Project count	Text Field count	Page Turning time
1000	100	14.20 s
		14.51 s
		21.37 s
		25.99 s
		23.61 s

Table 10: Paging 1 K, text field 1;

View Project count	Text Field count	Page Turning time
1000	1	2.81 s
		2.96 s
		2.92 s
		2.72 s
		2.89 s

10. Insert 100 million test data and 100 million text fields in a single line. The insertion time is as follows:

11. The data volume is 100 million, and the number of text fields in a single row is 100. The test data is shown in the following table:

Table 11: Page 1 K, text field 1;

View Project count	Text Field count	Page Turning time
1000	1	2.78 s
		3.04 s
		2.90 s
		2.95 s
		2.91 s

Table 12: Page 500, text field 100;

View Project count	Text Field count	Page Turning time
500	100	7.15 s
		7.35 s
		6.91 s
		7.24 s
		7.25 s

Table 13: page 100, text field 100;

View Project count	Text Field count	Page Turning time
100	100	1.96 s
		1.76 s
		1.68 s
		1.54 s
		1.61 s

Conclusion

Through the above test data, I personally think that the lookup field takes the longest query time, and a single line of text should belong to the category with less query time, therefore, the query efficiency has little to do with the number of projects in the List (not exceeding the list threshold value, within). It has a great relationship with the number of single queries, the number of fields in the view, and the field type in the view.

Summary

Through the above tests, I personally think that the Sharepoint list processes millions of data. It should be said that the pressure is not great. Because the data insertion speed is slow, more data levels will be tested later, and the list efficiency will be broken when the permission is disabled, for more information, see the following blog.

Test big data in the SharePoint 2013 list <2>