Good afternoon
very strange request from you.
don't you have any CCR with BGP in production ?
aren't you "The Largest Carrier-Grade MikroTik Integrator in North America" ?
best regards
Thierry

Touche!...you are correct, we ARE the largest Carrier-Grade Integrator in North America and deploy BGP/MPLS solutions to many large wireline/wisp carriers. We work with a lot of CCRs in BGP peering and have seen various issues. We tend to limit full table peerings on CCRs to no more than 2 based on the limitation of a multi-threaded BGP process. Since we are an integrator, most of our customers use Cisco and Juniper still for public BGP peering and are reluctant to migrate. Large carriers don't like being beta testers in general - stability and conservative design is the name of the game.
The intent of the thread is to try and centralize information and experiences on peering with full global BGP tables on CCR and see if there are common issues across software versions and/or types of peering routers.
So with your experience you may know that
1) bgp needs a lot of cpu
2) bgp needs some memory
3) V6.x is not multi thread for BGP
but to help you
CCR1036-4G can handle with no problem 2 full table IPV4 + IPV6
if you need a lot of peers use x86 until v7 and 72 tilera cores
for compatibility as you seem not to be able to do testings it works fine with cisco, juniper, quagga, bird, huawey
our network is spread over europe with 9 bgp routers ( x86 ) with about 500 bgp sessions including peering and upstreams
it takes about 1 minute to propagate a full IPV4 table over all the network
you will not be able to do this even with SUP720 3BXL or MX80 ( we have tested in real production )
for public peering if you are connected on a peering point like AMSIX, DECIX, TOPIX, LUCIX ... you will see a lot of Mikrotik routers just with "ip neighbour" but they are not speaking about it
our customers are using CCR for connecting their upstreams and they have no issue but the secret is also about setup
regards
Thierry