Active Directory Maximum Limits and Scalability topic updated

The Active Directory Maximum Limits and Scalability topic has been recently updated to reflect improvements in Windows Server 2012 to the number of RIDs that can be allocated over the lifetime of a domain. Another update was made to the section about maximum number of objects to reflect garbage collection batch size, which is 5000. Someone asked if it was advisable to increase garbage collection volume by increasing the size of the batches over 5000. And the answer from an AD developer was no, it’s better to manually trigger the operational attribute dogarbageCollection=1 and garbageCollPeriod to speed it up. See the topic for more details and links to related articles.

This Active Directory Maximum Limits and Scalability topic was originally written by Kurt Hudson and has helped answer a lot of related questions over the past several years. Hopefully users will continue to discover it and find it useful.



Justin [Active Directory Documentation Team]

Comments (2)

  1. I (and others) frequently link to this article when answering questions in the forums. Thanks for updating it.

  2. I would say that the GC task is rescheduled immediately (allowing other tasks to enter the task queue) once a single pass have processed 5000 (expired deleted objects/phantoms, expired recycled objects/phantoms, expired absent link values and expired dynamic objects (combined) in the pass) – The limit is enforced to statisfy database (ESE) layer transacations. – So it's inaccurate that we have to wait 12h for another pass. See table 'Table 17: Garbage Collector background task reschedule' in…/how-the-active-directory-data-store-really-works-inside-ntds.dit-part-4