When possible, try to use separate disk drives for the source data being indexed and the index files outputted from the indexer. Local data also removes the network connection as a possible point of failure during a long indexing session. Generating the required indexes involves a high amount of disk read and some write activity, and by using a local internal drive you can gain a significant performance boost over using an external drive or remote location. It is strongly recommended that you store the data to be indexed locally, on the same machine as the Zoom Indexer is running from. Disk and Storage considerations Store sample data locally if possible See this Microsoft Knowledge Base article (121007) for help on how to disable this feature. Although doing this can help to increase directory enumeration performance, some 16-bit applications may not be able to find files and directories with long filenames, but this should not be an issue if you are running a 64bit O/S. Disable 8.3 filenamesĪnother way of improving NTFS performance is to disable the creation of 8.3 filenames and directories.
This type of organization is recommended as NTFS can often become unstable or unresponsive if an individual folder contains too many files. At most folders should only ever contain a few thousand folders or files.
The content to be indexed should be organized into a practical and multi-tiered structure. It also includes a real-life case study of indexing all of Wikipedia and information about dedicated search appliances.įor the purposes of this article, an enormous site is one that has 500,000 or more pages, and/or 500 million or more words.įile and Folder structure Store sample data in a organized manner This page covers a number of hints and tips that should make the job quicker and easier. Indexing huge amounts of data can be a big job.
0 kommentar(er)
