Donald Sharp

There is no `code compliance` issue. The rp pim keep alive timer is 210 seconds. There is nothing in the code that lists it as 185. This is a straight...

https://github.com/FRRouting/frr/wiki/Perf-Recording can we get a flame-graph for bgpd and zebra?

@mauroalx -> Can you gather the flame-graph as outlined in the perf-recording? Alternatively can you send me a ipv6 labeled unicast feed? ( we can work off github to get...

I was able to recreate a perf issue( probably the same but we'll see ). ```[5:33 PM] 50.69% libfrr.so.0.0.0 [.] default_cmp 45.29% libfrr.so.0.0.0 [.] skiplist_insert 3.24% bgpd [.] get_label_from_pool 0.31%...

when I was testing this behavior last night, I noticed that bgp was restarting every 25-30 minutes because watchfrr was unable to get to it due to the performance issue....

yes a perf record would still be good. The `watchfrr ignore bgpd` is just to allow everything to stabilize after a fairly long time

let's get warnings cleaned up as well.

FRR does not currently have the ability to track nexthops against a particular table. Someone would need to implement this feature

@yar-fed -> I believe I fixed this issue already. Can you please try the problem on latest master without your code to see if it still exists?

If the issue still exists can you give me a sequence of commands that shows the problem so I may understand what I am mising better?