Bug #241
remove a comment about ACACHE in named.conf
| Status: | Closed | Start date: | 08/22/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | - | Spent time: | 1.00 hour | |
| Target version: | 1st Public Cerowrt release |
Description
You don't want ACACHE.
:)
acache will speed authoritative replies at the cost of memory. A home router is likely scaled poorly for RAM and has decent enough speed to handle looking up normally. I'd remove the comment and avoid the ACACHE feature in BIND 9.
History
Updated by Dave Täht almost 2 years ago
In my case I was often attempting to optimize for living in the 3rd world where 300ms dns R/Ts are common. So adding cache is a GOOD thing. At present, bind9 is using about 24MB of ram, with about 32MB of ram left over for other stuff.
Secondly, what I'd like to be doing at some point soon is benchmarking bind9 vs dnsmasq and seeing what can be optimized.
Updated by Dave Täht almost 2 years ago
so I would be interested in using the built-in "netem" network emulator to simulate and analyze the effect of varying levels of delay on bind9.
In the interim, how do you actually use acache?
Updated by Michael Graff over 1 year ago
acache just pre-renders the wire-format response, it does not add additional non-CPU saving performance.
It also only handles authority responses, so the RTT is still there.
You really don't want this unless you are planning on handling a metric crapload of queries/sec.
Updated by Dave Täht over 1 year ago
- Status changed from New to Closed
- Target version set to 1st Public Cerowrt release
- % Done changed from 0 to 100
ok, I will remove this comment in rc6. However, any performance boosting ideas remain welcomed.