Thanks Doug. Yes, helps a lot. And yes, this is to handle adding new zones. <div><br></div><div>Glad I'm on the right track :) I should point out that those ideas came from trawling this and many other forums!<div><br>
</div><div>I should also point out that when I said "short-term fix", I meant these were changes we could implement relatively quickly compared to upgrading hardware. These fixes would certainly remain in place for the long term.</div>
<div><br></div><div>600,000 zones!! Can I ask what type of hardware you were using? We are unfortunately running on old h/w and o/s - hp dl380 g4 with FreeBSD 6. So any other tips for optimisation would be greatly appreciated.</div>
<div><br></div><div>DP<br><br><div class="gmail_quote">On Sun, Feb 27, 2011 at 3:22 PM, Doug Barton <span dir="ltr"><<a href="mailto:dougb@dougbarton.us">dougb@dougbarton.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 02/26/2011 18:56, Dennis Perisa wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi folks,<br>
<br>
I'm looking for suggestions to substantially improve reload times on a<br>
slave that is serving 50,000 zones (mostly customer zones).<br>
<br>
'rndc reload' is being executed on the slave every 15 minutes.<br>
</blockquote>
<br></div>
Yeah, don't do that. :) Is this being done to handle updates to customer zones? If so, you're much better off to reload them individually (rndc reload zonename), or better yet use dynamic updates. If you're doing this for other reasons you need to expand.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Due to<br>
the large number of zones to trawl through, the reload process is<br>
causing intermittent outages and/or significant delays to zone transfers.<br>
</blockquote>
<br></div>
Familiar problem.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Here are some ideas I have:<br>
- use rndc reconfig instead<br>
</blockquote>
<br></div>
This sounds like you're trying to handle _adding_ new customer zones. In that case, yes you're much better off with reconfig.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- separate zone files into separate dirs to improve O/S performance<br>
(currently, all zone files are in a single dir)<br>
</blockquote>
<br></div>
Depending on your OS this can help quite a bit. 10k files in one directory is the point where you can start to see problems, so 50k is likely well past this point. I had a structure with one level based on the first character of the domain, and the next level based on the first 2 characters. That way you should be able to keep all the directories down to less than 5k files (due to uneven distribution of first characters in domain names).<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Are these viable options? Any other thoughts/suggestions?<br>
</blockquote>
<br></div>
I did all 3 of these things in the past to handle over 600,000 zones, so you're definitely on the right track.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is expected to be a short-term fix while we consider brute force<br>
approach of throwing more cpu/mem/IO at this.<br>
</blockquote>
<br></div>
Depending on how much you plan to grow going forward you probably shouldn't consider these short-term steps.<br>
<br>
<br>
hth,<br>
<br>
Doug<br><font color="#888888">
<br>
-- <br>
<br>
Nothin' ever doesn't change, but nothin' changes much.<br>
-- OK Go<br>
<br>
Breadth of IT experience, and depth of knowledge in the DNS.<br>
Yours for the right price. :) <a href="http://SupersetSolutions.com/" target="_blank">http://SupersetSolutions.com/</a><br>
<br>
</font></blockquote></div><br></div></div>