How to avoid the Top 5 SharePoint Performance Mistakes
In this blog post
- #1: Iterating through SPList Items
- #2: Requesting too much data from the content database
- #3: Memory Leaks with SPSite and SPWeb
- #4: Index Columns are not necessarily improving performance
- #5: SharePoint is not a relational database for high volume transactional processing
- Final words
Share blog post
Update Nov 27, 2014: Just posted this YouTube video that shows how to easily identify top SharePoint Performance Problems: SharePoint Performance Analysis in 15 Minutes
SharePoint is without question a fast-growing platform and Microsoft is making lots of money with it. Its been around for almost a decade and grew from a small list and document management application into an application development platform on top of ASP.NET using its own API to manage content in the SharePoint Content Database.
Over the years many things have changed but some havent like SharePoint still uses a single database table to store ALL items in any SharePoint List. And this brings me straight into the #1 problem I have seen when working with companies that implemented their own solution based on SharePoint.
The following blog shows my findings mainly using Dynatrace which you can also download and use for free on your environment.
#1: Iterating through SPList Items
As a developer I get access to a SPList object either using it from my current SPContext or creating a SPList object to access a list identified by its name. SPList provides an Items property that returns a SPListItemCollection object. The following code snippet shows one way to display the Title column of the first 100 items in the current SPList object:
SPList activeList = SPContext.Current.List; for[int i=0;i