public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Jordan Savoca <jsavoca@posteo.net>
To: location@lists.ipfire.org
Subject: Re: Reduced AS/route visibility
Date: Fri, 22 Mar 2024 16:54:02 +0000	[thread overview]
Message-ID: <D00FP7J0SB3M.1L3HLXY47RA1X@posteo.net> (raw)
In-Reply-To: <A87F8A5C-89E4-4706-892B-0C884343F6B6@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

On Fri Mar 22, 2024 at 9:34 AM MST, Michael Tremer wrote:
> Very cool.
>
> Any reason why you are parsing the text file instead of using our Python bindings?

No reason beyond a highly unproductive preference for few dependencies
and regrettable fondness for quick parsing scripts. :P

My production systems are Alpine-based and I tend to use shared systems
for development where there's considerable resistance to installing
dependencies system-wide, so it's usually easiest to use the packages
already available on the system or those easily installable in userland.

> The text file isn’t flat so you cannot only search to the first match, but since the binary database is organised as a tree, a search will be a lot faster and accurate. The bindings are packaged for Fedora, Debian and a couple of others.
>
> If you want to have all networks that belong to a specific AS, there is a way to search for them having the library walk through the entire tree. That should be super fast.

This is a good point, though. Ideally I wouldn't be systematically
discarding swaths of announcement information and incurring performance
costs during queries for more or less no reason.

> No worries. As mentioned we had a couple of outstanding issues and I believe that they are now all solved which will help us pave the way for a 1.0 release.
>
> Great to see that the database is making its way into projects everywhere :)

Definitely! Looking forward to the 1.0 release. :) Thanks again.

--
Jordan

  reply	other threads:[~2024-03-22 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22  4:03 Jordan Savoca
2024-03-22 16:09 ` Michael Tremer
2024-03-22 16:21   ` Jordan Savoca
2024-03-22 16:27   ` Jordan Savoca
2024-03-22 16:34     ` Michael Tremer
2024-03-22 16:54       ` Jordan Savoca [this message]
2024-03-22 16:55         ` Michael Tremer

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=D00FP7J0SB3M.1L3HLXY47RA1X@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