Once a virtual search server has been accessed, all of its configuration files are read into memory. For speed reasons, the virtual search server remains cached in memory until a period of inactivity has elapsed. The virtual search server is then dynamically removed from memory until its next use. Because of this, the first time a virtual search server 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:
Adjusting any of these values can have a significant impact on the performance of your search services.
As a general guideline, use the fastest CPU possible and include as much RAM as possible. Although the duration of each user query is very short, while it is active it consumes an average of 500 KB of memory. Memory consumption varies widely while the indexer is calculating the final search results list, depending on the number of possible search results.
Also, try to schedule the regeneration of your indexes during off-peak hours. That way, they won't interfere with normal user searches. (See Automating Index and Server Maintenance.)
If you find that your users frequently enter search words such as to, of, a, the, in, etc., you might want to consider removing these words before they are submitted to the Web Search engine.
HINT: A stop-words processor is available in the Enterprise version of Web Search. Contact your local Novell resale representive for more information.