re: Taking Out The Trash

Gennady Efimov - ge][ — Wed, 09 Dec 2009 05:50:04 GMT

Garbage Collection Scheduling Enhancements

The process for completing garbage collection has changed in Windows Server 2003 to improve storage conditions in the directory database. Garbage collection removes a maximum of 5,000 objects per pass to avoid indefinitely delaying other directory service tasks. However, the rate at which remaining tombstones are deleted when more than 5,000 tombstones have expired has increased from Windows 2000 Server to Windows Server 2003, as follows:

Windows 2000 Server: If collection stops because of the 5,000-object limit (rather than by running out of objects to collect), the next garbage collection pass is scheduled for half the normal garbage collection interval (by default, every 6 hours instead of 12 hours). Garbage collection continues running at this accelerated pace until all objects have been collected.

Windows Server 2003: Rather than waiting a set time to remove a subsequent set of 5,000 tombstones, a domain controller continues deleting tombstones according to CPU availability. If no other process is using the CPU, garbage collection proceeds. Removing tombstones in this way keeps the database size from increasing inordinately as a result of the inability of garbage collection to fully complete removal of all tombstones during a garbage collection interval.

re: Taking Out The Trash

jansenet — Tue, 24 Mar 2009 21:29:49 GMT

Tim,

It sounds like the same logic is used when it comes to the garbage collections thats used during a GC tear down as far as the pre-emptions and priorities. You had some good tidbits in there that I didn't know. Great article! Keep em coming! :)

Thanks,

Eric