Re: Reduced AS/route visibility

[Michael Tremer <michael.tremer@ipfire.org>]

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

Hey,

> On 22 Mar 2024, at 16:54, Jordan Savoca <jsavoca(a)posteo.net> wrote:
> 
> 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.

Yeah, I have spent a lot of time to make the search really really fast. So it would be good to see that code in hefty use :)

>> 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