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.

600 Part VII: Information Management in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

Incremental (Inclusive) Update<br />

SharePoint Portal Server 2003 changed the incremental update to make it more efficient<br />

<strong>and</strong> less resource intensive. To allow for changes that the incremental update<br />

does not check for, SharePoint Portal Server 2003 included a new type of update<br />

called the incremental (inclusive) update. This update is similar to the incremental<br />

update except that the incremental (inclusive) update removes deleted content from<br />

the index. Otherwise, this update is similar to the incremental update in SharePoint<br />

Portal Server 2001. The incremental (inclusive) update is more resource intensive<br />

than the regular incremental update <strong>and</strong> should therefore be run less often. The<br />

incremental update is the least resource-intensive update.<br />

Adaptive Update<br />

An adaptive update builds a statistical model for the content source <strong>and</strong> crawls only<br />

the content that, statistically speaking, is more likely to have changed since the last<br />

update. Unlike the incremental update, the adaptive update increases its efficiency<br />

by “learning” which content changes <strong>and</strong> at what frequency, <strong>and</strong> then it molds its<br />

crawling schedule accordingly.<br />

How Adaptive Updates Work<br />

To decide which documents to crawl, adaptive updates gather change information<br />

each time an update is performed on a content source. This information is used to<br />

determine which documents are most likely to change. Because of this, the efficiency<br />

of adaptive updates increases over time <strong>and</strong> over multiple updates. As more<br />

updates are performed, more statistical samples are available to the algorithm. After<br />

a week of daily adaptive updates, the system settles into a steady state. A steady<br />

state is a state in which the system has acquired enough information for the adaptive<br />

update to function at optimal efficiency.<br />

Improving Performance with Adaptive Updates<br />

The algorithm used by adaptive updates computes statistical information regardless<br />

of the type of update SharePoint Portal Server performs. If incremental updates are<br />

run first <strong>and</strong> then later adaptive updates are used, performance improves immediately<br />

because the system is already in a steady state. This is because SharePoint<br />

Portal Server has already accumulated sufficient statistical information to apply the<br />

algorithm.<br />

Performance improvement between an adaptive update <strong>and</strong> an incremental<br />

update depends on the number of documents <strong>and</strong> the frequency of changes to the<br />

documents. The higher the percentage of documents that change infrequently, the<br />

better the performance is. Adaptive updates show the most significant performance<br />

improvement in collections of more than 2500 documents.

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

Saved successfully!

Ooh no, something went wrong!