| There are some tasks that require special consideration and careful planning. Some tasks are classified as long-running operations, such as such as moving, copying, or deleting folders; deleting or renaming categories; creating content sources; and changing inherited security. Table 6.7 provides example calculations for certain tasks that require special consideration: Table 6.7. Performance Expectations Matrix | Function | Performance Expectation | Description | | Changing role membership | ~3 folders per/second | When copying a folder, all documents and sub-folders are copied at an approximate rate of two files per second. Copying 10,000 documents is estimated to take approximately 1.3 hours. | | Renaming Categories | ~5 documents per second | When categories are renamed , all categorization data for all documents belonging to the categories is updated. For example, if your category hierarchy consists of 50 categories and 20 documents within in each category, the entire category hierarchy can be modified in approximately 3 minutes 33 seconds. | | Crawling | ~12 “18 documents per second | For the most common document types, a quad-processor can crawl 12 “18 documents per second. If you are crawling 500,000 documents, the initial crawl process will take 12 hours. With the use of adaptive updates, you can decrease crawling time by 6x. In our example, you would be able to crawl the 500,000 documents within two hours using the Adaptive Update process. | | Search | <5 seconds | The optimal throughput of searches from the dashboard site varies depending on the number of documents included in the index. It is important to ensure sufficient RAM for the database cache to achieve optimal throughput for searches. A quad-processor 500MHz server with 2GB of RAM and 3.5 million documents included in the index can respond to 95% of all searches in less than five seconds, with a maximum throughput of 20 searches per minute. | | Index Propagation | 60 seconds per 20K documents | The amount of time required to propagate an index to the dashboard server can vary depending on the kinds of documents included in the index, and the amount of metadata in the index. Typically, propagation takes one minute for every 20,000 documents in the index. | NOTE The preceding recommendations were made assuming a multi-processor 500MHz Pentium III with 2GB of RAM being used.
Adaptive updates are discussed in detail in Chapter 19.  |
