16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 10: Performance Monitoring in <strong>Microsoft</strong> Office SharePoint Portal Server 2003 243<br />

Leading Indicators for Index Servers<br />

The key performance thresholds for index servers are 80 to 85 percent processor<br />

time <strong>and</strong> 85 percent memory availability. However, the decision to add an index<br />

server is more a function of indexing <strong>and</strong> propagation time than of monitoring performance<br />

counters. When indexing <strong>and</strong> propagation cannot proceed fast enough to<br />

keep content indexes as up to date as your customer’s business requirements<br />

dem<strong>and</strong>, you should add another index server. For example, if it takes two hours for<br />

an incremental crawl <strong>and</strong> propagation when you need half-hour updates, consider<br />

adding an index server.<br />

Factors Influencing Index Server Performance<br />

Depending on business requirements, it might be acceptable to have as many as<br />

5 million documents in one content index, but if the rate of change is high <strong>and</strong> alerts<br />

are popular, you might need two or three index servers for that data. Performance<br />

of an index server also depends on the location of the crawled content <strong>and</strong> the processing<br />

power of the index server. Crawl times depend on many factors, including<br />

the following ones:<br />

■ Content location <strong>and</strong> network performance. Content location <strong>and</strong> network<br />

performance are related. For example, when crawling content outside of<br />

your corporate LAN, performance might slow down. Crawling sites within your<br />

intranet with adequate b<strong>and</strong>width is generally faster.<br />

■ Type of documents in the index. You might be crawling sites that contain<br />

a variety of document types, such as <strong>Microsoft</strong> Word, Excel, or Visio, in<br />

addition to HTML files. Some file types are more resource intensive than<br />

others.<br />

■ Frequency <strong>and</strong> type of content index updates. The update schedule can<br />

be as frequent as a weekly full update with an incremental crawl every 15 minutes<br />

or something much less aggressive. You might be able to improve indexing<br />

performance by adjusting your crawling schedule to crawl less frequently<br />

if this can be done without affecting your ability to meet the business<br />

requirements.<br />

Scale-Out Limitations for Index Servers<br />

If your existing architecture is a medium server farm, adding an index server<br />

requires that you scale to a large server farm. This also requires the implementation<br />

of two dedicated search servers, which is the minimum supported configuration for<br />

a large server farm.<br />

<strong>Microsoft</strong> recommends no more than four index servers per large server farm.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!