Hi all, We have previously used CCRs for BGP transit peers, but found that the delay in BGP with global routes updating the routing table was slower than we would like. This was mainly due to the fact that the BGP process only runs on a single thread so even a upgrading to a CCR1072 is not going to improve it. We built a couple of CHRs with iBGP between them. They perform better because each individual core is faster than the CCR cores, but they still really struggle when there are significant changes to the route table. One of the CPU cores sits at 100% for an extended period of time while the other core sits at almost nothing, and occasionally all of the BGP peers to drop their sessions from timeouts while it is in this state. As the peers re-establish, the route table has a lot more updates to process and so we get in a bit of a vicious circle until the it can manage to get through it all. Does anyone else have experience with global route tables (preferably multiple) on RouterOS? Does anyone have any advice on how we can increase the performance? Throwing more cores at the CHRs doesn't seem like it would have much benefit, but is something we have been considering. We are open to suggestions of alternative platforms to replace or integrate with the design. Waiting for RouterOS v7 which is meant to be more multithreaded might be an option if we had an actual ETA on it.... :) Regards, Philip Loenneker | Network Engineer | TasmaNet 40-50 Innovation Drive, Dowsing Point, Tas 7010, Australia P: 03 6165 2542 | M: 0404 097 816 philip.loenneker@tasmanet.com.au<mailto:philip.loenneker@tasmanet.com.au> www.tasmanet.com.au<http://www.tasmanet.com.au/>