The Locator Server can impact business systems in three distinct ways:
Initial Indexing
Incremental Indexing
After the initial indexing has completed, updates will only occur for added, deleted, or changed data. The Locator Server may be periodically busy when new documents are processed, but this rarely creates a network performance impact. By scheduling incremental indexing during "off-shift" hours, users will see little, if any, degradation of system performance. During periods of incremental indexing, the amount of data indexed is normally too small to adversely impact overall system performance, including the Locator Server itself or any other system components.
After the initial indexing has completed, updates will only occur for added, deleted, or changed data. The Locator Server may be periodically busy when new documents are processed, but this rarely creates a network performance impact. By scheduling incremental indexing during "off-shift" hours, users will see little, if any, degradation of system performance. During periods of incremental indexing, the amount of data indexed is normally too small to adversely impact overall system performance, including the Locator Server itself or any other system components.
...
| Impact On: | Initial Indexing | Incremental Indexing | User Searches |
|---|---|---|---|
| Locator Server | High Impact Normally high loads on CPU, RAM and disk during this phase | Possible High Impact Possibly high loads on CPU, RAM and disks during scheduled periods | Low Impact IIS (Internet Information Services) web service response is critical |
| Target/Source Server | Low to Medium Impact | Low Impact Periodically only | Low Impact Security response from the target/source server is critical |
| Network Traffic | Medium Impact Increased network traffic while doing this task | Low Impact Periodically only | No Impact Might even decrease network traffic by reducing file browsing |
See also
| Child pages (Children Display) | ||
|---|---|---|
|
...