|
|
DirectoryService high CPU utilization
Thanks for your hint! Apple moved moved DNS lookups to the DirectoryService daemon in Snow Leopard, and since then I've noticed the same problem with the high %CPU. For those who say that they don't notice the hit, try refreshing 200+ feeds from an RSS reader while keeping an eye on the CPU. The drag on the system caused by DirectoryService grepping the /etc/hosts file for _every_ domain lookup is quite obvious then, but the little hits from every-day browsing also add up to quite a bit. I tried to resolve it :), like you, by installing a local nameserver, but I installed unbound, which is a very powerful recursive DNS server. It was a bit too powerful though, and it was clear that it was optimized for extremely heavy workloads on the public internet, aggressively caching and generally not staying as quiescent as I hoped. So I went unhappily back to the hosts file. Luckily I ran across your hint today and installed dnsmasq from source. It's perfect, and exactly what I was erroneously looking for from unbound. You should note, though, that people who use the hosts file for adblocking should take the following steps for the best results:
So thanks again. I'm feeling much happier with this setup. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|