| Performance Tuning Microsoft Indexing
Services (Index Server)
(for Windows 2000 Server, Windows Server 2003)
Companion Search scripts:
-
ASP Search for Index Server
- ASP.NET Search for Index Server
Microsoft Indexing Services (Index Server):
To learn how to configure Microsoft Indexing Services for either
Windows 2000 Server or Windows Server 2003, visit the "Index
Server Tutorial" page by clicking here.
Why Tune Performance?
A common question for many Indexing Service users is how often
the Indexing Service is updated. Is it automatic, manual,
done every hour, minute, second, do they have to restart the
service?
For all intents and purposes, changes to an indexed document
are instant and automatic. However, how instant is determined
by the size of the index and server resources.
So, Microsoft have provided a simple tool to allow the administrator
to set the relative importance of these updates. How important
it should be for the Index to be current at any point in time
and how many queries should the server typically expect to
answer. Of course, you can set both of these to their maximum,
but this will be at the expense of other services running
on the server.
| 
|
|
 |
| |
5. Customizing Indexing Service usage:
If you'd prefer to have more control, you can select
"Customize" from the option list shown in
Fig.3.
- The "Indexing" slider determines how
quickly the Indexing Service reacts to document changes
or additions.
- The "Querying" slider determines how quickly
Indexing Service processes queries.
For example: If your index must be absolutely current
at all times but not many search queries are typically
submitted - an "Instant" setting for "Indexing"
and a "Low load" setting for "Querying"
will be required.
Finally, to ensure that your changes take effect, you
should restart the Indexing Service. |
|
 |
|
 |
|
