Understanding and Configuring Registry Size Limit (RSL)

 Last reviewed: December 29, 1997
Article ID: Q124594

The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SUMMARY

The total amount of space that may be consumed in paged pool and disk space by Registry data (the Hives) is limited by the Registry Size Limit, or RSL. RSL is a kind of "global quota" for Registry space.

MORE INFORMATION

By default, RSL is 25 percent of the size of paged pool. Setting up the size of paged pool (see PagedPoolSize value of the Registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management) also affects the size of RSL.

You can also manually set the RSL:

  1. Run the Registry Editor (REGEDT32.EXE).

WARNING: Using Registry Editor incorrectly can cause serious, system-wide 
   problems that may require you to reinstall Windows NT to correct them.
   Microsoft cannot guarantee that any problems resulting from the use of
   Registry Editor can be solved. Use this tool at your own risk.

  • Locate the key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control.

  • Modify the value RegistrySizeLimit (create it first it if it does not already exist) to reflect the desired size, in terms of bytes.

    NOTE: RegistrySizeLimit must have a type of REG_DWORD, and a data length of 4 bytes, or it is ignored. If you set the value RegistrySizeLimit to less than 4 megabytes (MB), it is forced up to 4 MB. If you set it to greater than about 80 percent of the size of paged pool, it is set down to 80 percent of the size of paged pool (it is assumed that paged pool is always more than 5 MB). If you set it to 0xffffffff the maximum size allowable (or 80 percent of paged pool, up to 102 MB) is set.

  • Shut down and restart Windows NT for changes in RSL to take effect.

    Additional Notes on RSL

    RSL sets a maximum, not an allocation (unlike some other such limits in the system). Setting a large RSL will NOT cause the system to use that much space unless it is actually needed by the Registry. It also does NOT guarantee that that much space will be available for use in the Registry.

    In Windows NT version 3.1, paged pool defaults to 32 MB, so the default RSL is 8 MB (enough to support approximately 5000 user accounts). In Windows NT 3.5, paged pool can be set to a maximum of 128 MB, so RSL can be no larger than about 102 MB (enough to support approximately 80,000 users; however, other system limitations might keep this number of users considerably lower).

    RSL includes space in the hives themselves, as well as some of the Registry's runtime structures. Other runtime structures are either billed against standard quota, or are protected by size limits and serialization.

    To ensure that you can always at least boot and edit the Registry if you set RSL incorrectly, quota checking is not turned on until after the first successful loading of a hive (that is, loading a user profile).

    For all but a few domain controllers, RSL never needs to be changed.

    The limitations imposed by RSL are approximate.

    For more information on the Registry size limit, search on the keyword "RegistrySizeLimit" in the Windows NT Registry Entries Help file found in the Windows NT version 3.5 Resource Kit, or query on the following keyword in the Microsoft Knowledge Base: 

       RSL

    • Additional reference words: prodnt 3.50
    KBCategory: kbnetwork
    KBSubcategory: ntregistry

    THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

    Last reviewed: December 29, 1997
    © 1998 Microsoft Corporation. All rights reserved. Terms of Use.