Re: Notice of plan to deprecate map zone file format

I am just going to point out that the 10 second speed up was measured on .net zone. Thus the calculations provided below have no practical impact because if anybody is loading 100k .net-sized zones on a single server they will have a different problem that the loading speed… The goal of the

Re: Notice of plan to deprecate map zone file format

For the record, there’s small typo below - the stable major version where we plan to remove the map format is 9.18. E.g. this will happen in the next stable release rather than in 9.20 that’s going to be released in ~2024. Ondrej -- Ondřej Surý — ISC (He/Him) My working hours and your working

Re: Notice of plan to deprecate map zone file format

On Fri, Sep 10, 2021 at 01:58:41PM -0400, Timothe Litt wrote: > In fact, were you to come up with a data structure and loading scheme > that made raw as fast as map, you could treat "map" as a hint that a > user values speed over size & portability - and just write raw format > instead.  Until the

Re: Notice of plan to deprecate map zone file format

On 10-Sep-21 13:11, Evan Hunt wrote: > Recently a critical bug was discovered in which map files that were > generated by a previous version of BIND caused a crash in newer versions. > It took over a month for anybody to report the bug to us, which suggests > that the number of people willing to

Re: Notice of plan to deprecate map zone file format

I'm not a consumer of this and agree that it's up to users to speak up, so I'll stop here - with one final observation. The issue comment containing the benchmarks includes: > Speedup provided by the |map| format does not seem significant enough > to warrant the complexity of map format,

Re: Notice of plan to deprecate map zone file format

On Fri, Sep 10, 2021 at 07:24:19AM -0400, Timothe Litt wrote: > Clearly map format solved a big problem for some users.  Asking whether > it's OK to drop it with no statement of what those users would give up > today is not reasonable. > > After all the "other improvements in performance" that

Re: Notice of plan to deprecate map zone file format

>>> After all the "other improvements in performance" that you cited, what is >>> the performance difference between map and the other formats? >> >> I don’t know that, to be honest. We don’t have the resources to benchmark >> everything. Maybe someone on this list could? We would also like

Re: Notice of plan to deprecate map zone file format

On 10-Sep-21 08:36, Victoria Risk wrote: > > >> On Sep 10, 2021, at 7:24 AM, Timothe Litt > > wrote: >> >> Clearly map format solved a big problem for some users.  Asking >> whether it's OK to drop it with no statement of what those users >> would give up today is not

Re: Notice of plan to deprecate map zone file format

> On Sep 10, 2021, at 7:24 AM, Timothe Litt wrote: > > Clearly map format solved a big problem for some users. Asking whether it's > OK to drop it with no statement of what those users would give up today is > not reasonable. > Actually, we are not sure there ARE any users. In fact, the

Re: BIND 'max-cache-size' Value on FreeBSD-13.0

On 9/10/21 12:35, sth...@nethelp.no wrote: Freebsd 12.2-STABLE here with servers running BIND 9.16.15, 9.16.18 and 9.16.20, all using libuv 1.41.0, all installed from ports. Typical query load from around 3k qps to around 14k qps. No sign of any memory leak. Would be interesting to hear

Re: Notice of plan to deprecate map zone file format

Vicky, I never reflexively "howl in protest", but it's really hard to have an opinion on this proposal without some data. Clearly map format solved a big problem for some users.  Asking whether it's OK to drop it with no statement of what those users would give up today is not reasonable. After

Re: BIND 'max-cache-size' Value on FreeBSD-13.0

>> 2.5 days in, and 9.11 is still running good, with no crashing. >> >> Safe to say that this memory leak is definitely an issue with 9.16. > > Which version of libuv are you using? I am running 1.41 and the latest is > 1.42. > > I haven’t seen that behavior and my recursives handle about

Re: BIND 'max-cache-size' Value on FreeBSD-13.0

On 9/10/21 10:29, Borja Marcos wrote: Which version of libuv are you using? I am running 1.41 and the latest is 1.42. I'm running libuv-1.41.0. I haven’t seen that behavior and my recursives handle about 100,000 requests per minute. Just in case I have updated libuv on one of them. I

Re: BIND 'max-cache-size' Value on FreeBSD-13.0

> On 9 Sep 2021, at 06:59, Mark Tinka wrote: > > 2.5 days in, and 9.11 is still running good, with no crashing. > > Safe to say that this memory leak is definitely an issue with 9.16. Which version of libuv are you using? I am running 1.41 and the latest is 1.42. I haven’t seen that

Re: Notice of plan to deprecate map zone file format

On 09/09/2021 21:13, Victoria Risk wrote: Hi Vicky, We would like to deprecate the `map` zone file format in future branches of BIND. The proposal is to deprecate the feature in the 9.16 branch, (users will see a warning when this feature is used but it will still work through the end of the