SharePoint: Performance Problem with LookupField Control
The upcoming standard Edit Form will use a LookupField control to display the current lookup value and the possible values taken from the referenced table.
Performance problem of LookupField control
It makes sense that the page rendering takes longer the more items there are in the referenced list. I was however surprised to find the page performance to be very slow when pressing the OK button on the edit page after you have made changes to your edited list item. I thought that this should be a rather quick operating – doing a simple update and then returning to my SharePoint list.
It turned out that submitting my changes took as long as requesting the edit form page. Looking insight into whats going on revealed the reason for that. It seems that the LookupField control also retrievs all items in case of a Page Postback – which happens when clicking the OK button. This might be intentional due to input value validation but it definitely slows down your page performance. The following PurePath shows what happens at the Page Postback:

On a page postback - the LookupField control spends 7 seconds in CreateChildControls where it queries the values to display
In my example above I had 1000 items in the referenced list – causing a page rendering and postback time of almost 10 seconds where 7 seconds where spent by the LookupField control.
Conclusion
I am not sure if this behavior is intentional. In any case you may want to think about using an alternativ control in case your lookup list contains a large number of items.
Related posts:
- SharePoint: Lookup value Performance In SharePoint you can define lookup columns in your lists....
- SharePoint: Page through SharePoint lists SharePoint lists can contain thousands of items. We have all heard...
- SharePoint: Using Batch-Updates to speed up performance? In my previous posts about SharePoint I focused on how...
- SharePoint ListItem Performance SharePoint provides a powerful object model to retrieve and manipulate...
- SharePoint: List Performance – How list column indices really work under the hood Have you ever wondered what is really going on under...

























[...] SharePoint: Performance Problem with LookupField Control [...]
I ran into this problem. The solution for that was to create an AJAX based Custom Field Control that filtered the list in the first place. Who would like to see a 1000 list items in a LookUp field?
Thanks for that comment – good workaround
I am sure Microsoft is also going to address the problem so that the control doesnt refetch all data upon the PostBack of the page
Cheers