[Unbound-users] TTL over cache-chunks
cifali.filipe at gmail.com
Mon Sep 1 14:00:18 UTC 2014
I'm seeing a behavior that I'm not sure is normal or I don't really
understood the meaning of cache-chunks.
Using multi-threads, is recommended to use the same number of chunks, based
on my tests, each chunk has is own cache for TTL and requests.
So, if I want to store cache only, I would need to use only one chunk of
cache. Is that correct?
In a multi-resolver scenario, I do like to put one unbound in front of
backend unbounds to cache de queries, but that would make him very
requested, that's why I searched about thread vs fork mode and was thinking
about using fork(even requiring more hardware, that's for the best
But I think I'm missing something, my configuration is basically:
E5405 8xCPU 2.00 Ghz
8 GB RAM
access-control: 127.0.0.0/8 allow
Filipe Cifali Stangler
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Unbound-users