North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: Scalability issues in the Internet routing system
Hey Andre,> I think you hit the nail on the head regarding record locking. This isNeat! So you were thinking you would leave the actual route selection process monolithic and create separate processes per peer? I have seen folks doing something similar with separate MBGP routing instances. Had not heard of anyone attempting this for a "global" routing table with separate threads per neighbor (as opposed to per table). What do you do if you have one neighbor who wants to send you all 2M routes though? I am thinking of route reflectors specifically but also confederation EIBGP sessions.
If you are intending to break the BGP process into per neighbor threads this does not sound like it would have beneficial impact on a single neighbor with the majority of the routes (thinking specifically of EIBGP and/or Route Reflectors). Was your idea specifically related to per neighbor processing or were you thinking you could break the BGP process itself into chunks?