From: Jordan Savoca <jsavoca@posteo.net>
To: location@lists.ipfire.org
Subject: Re: Auto-generated plaintext updates; re: regression
Date: Thu, 10 Mar 2022 16:02:03 +0000 [thread overview]
Message-ID: <e4f90668-e623-cf4b-5dfa-344a18e1c6ae@posteo.net> (raw)
In-Reply-To: <7433146A-A01A-49CE-A54C-AE5E33372D12@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
On 3/10/22 07:48, Michael Tremer wrote:
> I would strongly recommend this, because parsing the text database and going with the first match is quite likely going to give you inaccurate results.
>
> The reason why we are going with a binary format is because it is organised as a binary tree and therefore can be searched *very* quickly. It also allows us to store multiple networks with the same start address, but a different prefix length which is what you won’t have in a relational database and therefore you will quite likely have inaccurate results.
Yes! I store block announcements w/ autonomous system table foreign keys
to support anycast networks and varied prefixes without relation to or
dependence on the order in which the set is parsed, albeit at a
performance cost as you suggested.
> We kept the library as small as possible and we are looking at upstreaming it to all major distributions because that will help integrating it into other software a lot easier. Any help with this would be greatly appreciated.
Very cool, that would be sweet.
--
Jordan Savoca
prev parent reply other threads:[~2022-03-10 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 23:42 Jordan Savoca
2022-03-10 9:15 ` Michael Tremer
2022-03-10 14:45 ` Jordan Savoca
2022-03-10 14:48 ` Michael Tremer
2022-03-10 16:02 ` Jordan Savoca [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4f90668-e623-cf4b-5dfa-344a18e1c6ae@posteo.net \
--to=jsavoca@posteo.net \
--cc=location@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox