My Short and to the (Share)Point thoughts

SharePoint Search – What does “Indexing Performance” mean?

When on client sites, I often get asked “What do the Indexer Performance settings actually mean?”

They are relating to the Office SharePoint Server Search service setting for the server running the Index role.

For those that don’t know, this is access via Central Admin >Operations > Services on Server.  Select the Server doing the Indexing and select the Office SharePoint Server Search service.

image

The Indexer Performance setting affects the number of threads for Server running the Office SharePoint Server Search service in Indexing mode uses when crawling content.

Taken from TechNet, the following Table shows a  what the indexer values actually mean.

 

Indexer Performance setting

Total threads available for crawling

Maximum threads available for crawling any particular host

Reduced

Number of processors on the index server

Number of processors on the index server

Partially reduced

4 times the number of processors on the index server

Number of processors on the index server plus 4

Maximum

16 times the number of processors on the index server

Number of processors on the index server plus 4

Note -  Crawler impact rules override the Indexer Performance setting, so you can throttle te search more if you want.

The setting you choose depends very much on your circumstances. Things like:

  • Server farm deployment (Single Server, small farm, large farm)
  • Server hardware Spec (specifically of your Index server)
  • Use of SharePoint (Collaboration, Content Browsing, etc.)

I have always took the stance of if you have a dedicated Index server, use it for that, so set it to Maximum.  Single server deployments of MOSS, are more tricky.  I would recommend Reduced, maybe Partially Reduced dependent on the use of your SharePoint server, e.g.  Heavy Collaboration – Reduced, Medium Content Browsing -Partially reduced.


The TSUF Explained

On a day to day basis, I'm troubleshooting SharePoint, SQL and Windows Server issues.  Amongst some of my Trinity Colleagues, I have become well known for my 1st port of call fix for any issue, the TSUF.

Let me explain, TSUF stands for Tom Short Universal Fix.  This actually means a server reboot, a power cycle, the 1 finger power button salute, “turning it off and on again”.

Having come from a support background, starting off on 1st line, I know the power of a reboot.  Many a in the past time I have uttered the priceless words “Have you tried turning off and back on again?” and many times it has worked.

So now I am trying to spread the gospel of the TSUF outside my close circle of colleagues.

The TSUF Fixes Everything*

I would like to let people know that I’m a serious IT Consultant\Engineer and always carefully evaluate and investigate any issues before acting the appropriate manner.  It just seems that many times the TSUF is applied and resolves the issue. 

I have done some research and I can confirm that my studies have shown that when the TSUF is applied, 75% of the time it works every time*.

*not actually correct.