16 Kvě
2019
16 Kvě
'19
14:28
On 11/05/2019 13.22, Christoph wrote:
Yes, we agree. So for the time being we switched back
to unbound where
we get around 50% cache hit rate with less than 1GB of cache size,
but we are looking forward to test your future version that comes with
a garbage collector.
Hi,
I've prepared experimental packages with a cache GC daemon. You can
currently find them in [knot-resolver-testing]. (version
4.0.0.1558007111.360311a5)
If you'd be interested in testing it, it'd be a great help to assess
whether there are any major issues with the approach or the daemon. I've
played with it a bit and I set the defaults to values that seemed to
work, more info in [PR!817].
To run the GC as a daemon that checks the cache in
/var/cache/knot-resolver every minute, use:
kr_cache_gc -c /var/cache/knot-resolver -d 60000
Thanks for you help!
[knot-resolver-testing] -
https://build.opensuse.org/package/show/home:CZ-NIC:knot-resolver-testing/k…
[PR!817] - https://gitlab.labs.nic.cz/knot/knot-resolver/merge_requests/817
--
Tomas Krizek
PGP: 4A8B A48C 2AED 933B D495 C509 A1FB A5F7 EF8C 4869
Testing it would tremendously help to expedite
the process because
garbage collection very dependent on the deployment, so first user is
what we exactly need at the moment!
yes, we can test if there is a debian repository for it (otherwise we
would wait for the releases reaching your stable repo) .