Novell NETWARE 6-DOCUMENTATION Manual page 2102

Ensuring Optimal Search Speed
This example directs Web Search to perform two completely separate
searches. The search results from the two queries are then merged based on the
relevance of the individual search results and the weighting of the respective
query that produced them.
Another example might be to give the search results from one index more or
less relevance than the search results of another index when performing a
multiple-index search. For example, the search results from Novell might be
more relevant than the search results from Novonyx.
To send multiple query items, these parameters must be grouped using a
number (#) at the end of the parameter name so they will be interpreted
properly. The numbering should begin at 0 or 1 and increment sequentially for
each additional query item.
Once a search site has been accessed, all of its configuration files are read into
memory. For speed reasons, the search site remains cached in memory until a
period of inactivity has elapsed. The search site is then dynamically removed
from memory until its next use. Because of this, the first time a search site is
accessed is usually the slowest.
However, there are other factors that can affect the performance of your Web
Search services. As with any software, the amout of system resources (CPU,
RAM, and hard drive) available affects Web Search Server performance. Web
Search speed depends on the following factors:
System processor speed
Number of processors
Amount of system memory (RAM)
Number of hosted search sites
Number of indexes within each search site
Number of files included within each index
Number of indexes included within each query
Number of queries performed at one time
Complexity of users' queries
Number of search results returned with each results page
Optimizing Search Results 173