Indexing settings for the FYI Server affect performance and capacity. We recommend that you read the entire topic before making any changes.
On the Settings tab, you can adjust the amount of memory the FYI Server uses for indexing. Indexing cache memory is only used during the indexing and reindexing process, then the memory is released back to the operating system when indexing is complete.
Large memory allocations index databases faster. However, it is important to consider how many clients or users will index or reindex a database at the same time. Do not over-commit memory to indexing instances.
To Calculate the Indexing Cache
We recommend you leave at least 512 MB of RAM free and allow the rest to be used by indexing when needed. To calculate the indexing cache, take the amount of memory you have available, subtract 512 MB, and divide the remainder by the number of users you will allow to index at one time. Use that number for the Indexing cache (MB) setting.
Set the maximum number of users allowed to index concurrently in the Maximum indexing instances setting. Indexing is processor intensive. We recommend that you allow only one indexing process per processor, reserving the additional processor for general purposes. Count each Xeon or Pentium HT processor as two processors. For instance, if you have dual Xeon server with 2GB of RAM, you could set the Maximum indexing instances setting to 3 and the Indexing cache setting to 512 MB. If you want to allocate more memory to the index cache for faster performance, then lower the number of indexing instances to avoid over-committing memory.
To Modify the Indexing Cache and Instances
1.Click the Settings tab.
2.In the Server Settings section under Indexing settings, click the megabytes in the Indexing cache (MB) row, and type or scroll to the indexing cache that you calculated in megabytes.
3.The Indexing cache (MB) setting defaults to 128 MB.
i.The Maximum indexing instances setting controls the number of simultaneous indexing processes allowed. The number of instances entered for this setting should be low to ensure processing is done on the server.
4.In the Maximum indexing instances row, click the number and instances, and type or scroll to the new number of instances.
5.Click Apply to save your settings.
|
If two users are concurrently indexing, the allocated indexing cache is per user. For example, if the Indexing cache (MB) is set to 679 MB, both users are allocated 679 MB of cache. |
