AVSMaxLoc Explained

  • Modified Date:
  • Article ID:000089037


AVSMaxLoc Explained


An index defaults to allowing just over four billion locations before rolling over to additional indexes. (This is around 19 GB in size, representing about five million typical documents.) However, you can change this default at an indexing service or per-vault basis.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
Location: HKLM\SOFTWARE\KVS\Enterprise Vault\Indexing\
Key: AVSMaxLoc (DWORD) decimal value between 500,000,000 and 4,294,000,000
Note: To set on a per-index basis, create a sub-key of \Indexing named using the specific vault entry id.
Reducing the maximum number of structural locations per index reduces the size of the indexes. However, it also increases the total number of indexes, and so it may slightly increase the overall capacity requirements. Creating more indexes may slow Discovery Accelerator searches by having to search additional indexes, if the indexes are still large enough to generate high levels of I/O activity.
Reducing the size of the indexes can provide the following benefits:
- Enables more efficient searching when date ranges are used.
- Reduces the memory requirements of searching the archive.
- Enables smaller sections of a vault index to be rebuilt if required, reducing rebuild time.
- Reduces the risk of index corruption impacting service.
- Potentially reduces the I/O load during Discovery searches, improving search times.
An ideal value for this key has not been set, however in many cases 500,000,000 has proven to be beneficial. Engineering is currently investigating the advantages and disadvantages of modifying this setting and it is generally recommended for CA and DA customers.
Note:  Starting with versions 7.0 SP3 and 2007 SP2 AVSMaxloc is now defaulted to 1 billion. Setting AVSMaxloc through the registry is no longer recommended or required.


Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)