I'm looking for more precise information for DHCP sizing and I'd appreciate any real-world information as well.
What I'm trying to find out is how much registry space one DHCP server requires at max capacity. I realize that a DHCP server puts information in the registry for each scope. What exactly it's supposed to put in there under any given circumstance is a little less clear. How much space it requires or a way to estimate how much possible space could be used is totally unclear. I did find some information about RSL (max registry size basically) and about Microsoft's case study with their DHCP usage. That's not enough information though.
I'd like to find out what my limits are. For example, I'm interested in what would happen if I put the entire 10.x.x.x netblock on a single DHCP server. Before you tell me that shouldn't happen because of fault tolerance or network topology, I can tell you that network bandwidth is not a problem I suffer from. Fault tolerance for DHCP is often done via settings and the 80/20 split concept, although at some point it's possible that one server would have to achieve 100% during a failure scenario. Also, what is 80% capacity for one server?
Enough of the rambling... If anyone could point me in a better direction, I'd appreciate it. At worst, if you have any tools that would help to measure registry impact, that would be appreciated. I haven't investigated that route yet, but suspect that sysinternals likely has something I can use. I'm interested in the theoretical and the folks that wrote the code.
Questions I need to answer:
What is the max possible impact of the DHCP application on the registry?
What is the practical limit of a DHCP server in quantifiable terms?
Additional question from me:
Does anyone have any documents they can point me to that give the possible registry impact when scaling a DHCP server?
TIA
(Happy New Year BTW to those following the Gregorian Calendarical system ;)
Al Mulnick
"I strive to be unique. Just like everybody else"
