Monthly Archives: January 2012

SharePoint 2007 People Picker performance issues

Every time when you want to grant permission for a user or group in a SharePoint application you will use this SharePoint people-picker interface.

clip_image002[4] clip_image004[4]

How does people-picker work?

When you type a keyword to find a user or a group, people-piker will first make a query on the content database and if there are no results, it will make the second LDAP query on the DC. More info in this article

Continue reading

Performance with SharePoint 2010 Large lists – List view throttling

SharePoint 2010 lists and libraries can hold a maximum number of 30,000,000 items. In a SharePoint site the list view threshold is 5000 for users and 20,000 for auditors and administrators.

SharePoint large list and libraries operations like Delete/Update are one of the top performance killers.

What can we do if the server is overloaded when we access large lists and libraries? One solution is list view throttling.

Continue reading

Performance and Blob Storage

Two months ago I was at a SharePoint conference where I saw a nice presentation of Dan Holme regarding blob storage.

As per Microsoft definition – a binary large object (BLOB) is a large block of data stored in a database that is known by its size and location instead of by its structure — for example a Microsoft Office 2010 document or a video file.

Continue reading

Good to know before starting to troubleshoot performance issues on SharePoint 2003

Before starting implementing performance counters, be sure you are not using one of the following options:

/3GB switch – is not supported

Reducing the size of the kernel mode memory buffers when in /3GB mode causes unacceptable

performance in Windows SharePoint Services file-transfer operations.

Web gardens IIS 6.0 Session State May Be Lost If You Use Web Gardens with ASP Applications

Priority Boost on SQL server – How to determine proper SQL Server configuration settings

By default, the priority boost setting is 0, which causes SQL Server to run at a normal priority whether you run SQL Server on a uniprocessor computer or on a symmetric multiprocessor (SMP) computer. If you set priority boost to 1, the SQL Server process runs at a high priority

Once you have removed all those options you can start implementing performance counters and start analyzing them.