You can modify settings to improve performance while creating indexes or for performing search queries.
Because creating and updating an index is a resource-intensive process, you can choose to have a separate server that is dedicated to creating and updating indexes. The workspace on this server is an index workspace. An index workspace is designed to manage only content sources. The index workspace does not use the document management capabilities of SharePoint Portal Server, such as checking in or checking out documents or versioning, nor does it provide a dashboard site.
On the computer hosting the dashboard site, adjust the resource usage of the server to "background."
This ensures that no background index-related tasks consume CPU resources and take away resources from the dashboard site and the Web Storage System. However, if you use your workspace for many search activities, you may want to adjust the Search resource usage to Dedicated instead. Figure 15.1 illustrates these settings.
Figure 15.1. Specifying resource usage
For high performance, the property store and property store log files must be on separate dedicated physical volumes. You cannot move property store files by using SharePoint Portal Server Administration in Microsoft Management Console (MMC). You must use Catutil.exe to move property store files and to change the location of log files for the property store.
SharePoint Portal Server provides a utility named Catutil.exe that you can use to move index files and property store files and to change the location of the log files for the property store. Property store files contain the metadata from documents. SharePoint Portal Server shares the log files across all workspaces on a server. By default, SharePoint Portal Server stores the property store file and log files in the following directory:
\Data\FTData\SharePointPortalServer directory.
By default, Catutil.exe is stored in the Program Files\Common Files\Microsoft Shared\MSSearch\Bin folder. However, if you install SharePoint Portal Server on a computer running Microsoft SQL Server 7 or SQL Server 2000, Catutil.exe is stored in the Program Files\Common Files\System\MSSearch\Bin folder.
Catutil.exe PROPSTORE SharePointPortalServer -m "D:\Store\sps.edb"
Catutil.exe PROPSTORE SharePointPortalServer -m "D:\Store\MyFileName.edb"
By default, Catutil.exe is stored in the Program Files\Common Files\Microsoft Shared\MSSearch\Bin folder. However, if you install SharePoint Portal Server on a computer running SQL Server 7 or SQL Server 2000, Catutil.exe is stored in the Program Files\Common Files\System\MSSearch\Bin folder.
Catutil.exe PROPSTORE SharePointPortalServer -l"E:\Log"
Do not change the location of the log files for the property store to the root of a directory. For example, do not change the location to D:\. MSSearch does not function properly if the files are on a directory root. If you have changed the location to a directory root and MSSearch no longer functions, change the location of the files to a subdirectory instead. For example, change the location to D:\Log Files.
If query performance is slow and the computer has processor memory available, you can increase performance by specifying that MSSearch keep the property store in memory.
It is recommended that you do not set the CacheSizeMin to a value more than fifty percent of the available memory. If the CacheSizeMin value is set too high, it causes all queries to the server to fail with the message, "Internal Server Error." In addition, the Subscriptions Summary Web Part displays the following message, "Failed to get subscriptions results." If you encounter either of these errors, set the CacheSizeMin parameter to a lower value and restart the Microsoft Search service.
Incorrectly editing the registry may severely damage your system. Back up the current version of the registry before making any changes. You should also back up any valued data on the computer.
The total address space for MSSearch is 2 GB. Do not type a value greater than 1.7 GB, even if you have 2 GB or more of RAM.