This is part of why the old systems that were mentioned only optimized the top n routes based on traffic flow (or other configurable metric), because the cost vs. benefit falls off greatly.ShaneOn Dec 5, 2024, at 12:52 PM, Andrey Slastenov <a.slastenov@gmail.com> wrote:
Greetings, Drew
We don't use GPUs, but we have worked on a similar project focused on traffic optimization. I would say that the ping issue is one of the top pain points, even more significant than route recalculation. The more routes you try to monitor and optimize, the more significant the problem will become.Regarding optimization itself, I don't think you would want to optimize the entire routing table at the same time. From a calculation perspective, I don't believe it's a major problem at this point. Please correct me if I'm wrong.
Regards,Andrey
чт, 5 дек. 2024 г. в 18:32, Drew Weaver <drew.weaver@thenap.com>:So back in the.. hell I don’t know like… early 2010s there was a push for ‘route optimization’ from products like RouteScience and the Avaya CNA and more recently whatever Noction is doing.
The big pain point for this technology at the time was that it could only optimize the top N egress routes due to how many probes it could send out and how many results it could process.
It seems like now with a modest GPU in a router you could pretty easily ‘optimize’ [to the extent that you believe this technology worked] pretty much the whole routing table.
We used these tools extensively back then and they actually worked pretty well in most cases. The biggest issue we ran into was people complaining that we pinged their IP addresses… which now a days seems like a great worst problem to have.
Anyway is anyone doing any work on implementing GPUs into the BGP decision making process? Seems like a no brainer.
-Drew
--
