/ip route print where ... slow

Hi All.

Is there any thoughts on the best way to investigate/check routing when feeding full BGP tables into a RB?

Using /ip route print where x.x.x.x in dst-address when trying to troubleshoot routing/route preference is a really slow and frustrating.

On my new CCR at least it gets locked to one CPU and doesn’t impact the unit too much. What do most people do?

I am thinking about a BGP feed to a VM with OpenBGPd?

Just wondering what others do…

I tip which doesn’t seem to stand out is to enclose the prefix with " 's

ip route print detail where dst-address="xx.xx.xx.xx/xx"

On a large route DB, this shouldn’t take more than a few seconds to complete.

Route lookups and routing table convergence is significantly faster when using the CHR as a border router.

Here is a presentation I did at MUM Europe in 2018 on that topic.
https://www.youtube.com/watch?v=xcgdGA1W_0o