On 9 October 2015 at 00:36, Phil Bedard <phil...@gmail.com> wrote: > Timos (now SROS) is all internal, no config knobs I am aware of, but the > whole system was built to be multithreaded from the beginning. Their vRR > implementation is very fast because it can distribute the neighbor sessions > across multiple cores. If you look at the vRR stuff they have put out there > are some more details.
I understood that it's not per neighbour, but it's like one process/task for rib-in, rib-out and keepalive. And routing-instances live in separate set of three processes/tasks. I guess it shouldn't be too hard to further split rib-out per update-group, but you'll quickly run out of cores and start to pay context switch tax. -- ++ytti _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp