I'm the DNS (and DHCP!) administrator for a large midwestern bank, and I like to keep current with software available for my platforms. A newer Beta version of BIND came online at the beginning of May, and I decided to compile it on my Mac, for use as the local DNS caching server. It compiled fine out of the box. But I wondered ... I have the Standard Apple Build Tools (gcc) and it does have optimization options that aren't picked up in the standard ./configure script. Here are the CFLAGS environment variables I set the next time around:
-mabi=altivec -maltivec -mcpu=7450 -mtune=G4 -faltivec -O3 -fast
For ./configure I ran with the --with-openssl option. On the Dual CPU machine at home, I'll also run it with --with-threads. The binary is about one-half the size from the original un-optimized BIND build, in spite of the unrolled loops. It also seems to handle load better, to the tune of ten percent or so, by my top guesstimation (queries vs. application time).
Mac OS X Hints
http://hints.macworld.com/article.php?story=2004051215264341