BGP and memory

Ron Buchalski rbuchals at hotmail.com
Wed Oct 13 17:58:46 UTC 1999


The problem is, it's probably cheaper to engineer a box with more low cost 
memory than it is to pay a high salary to a programmer to write small code.

At least, it is in _this_ part of the world...  ;-)

-rb

>From: "Alex P. Rudnev" <alex at virgin.relcom.eu.net>
>To: nanog at merit.edu
>Subject: BGP and memory
>Date: Wed, 13 Oct 1999 18:22:30 +0400 (MSD)
>
>
>Amazing fact:
>
>Come back to this talks about BGP and memory, I calculated the size of
>total BGP information in the 'show ip bgp' cisco output. No doubt, it's
>not all attributes printed here, but on the other hand it's the text view,
>not the binary presentation.
>
>Results are:
>
>  118113 lines
>  10065161 bytes (10Mb)
>
>100 bytes/route , in the text form, average.
>
>Compare to
>
>65955 network entries and 159898 paths using 12154642 bytes of memory
>31322 BGP path attribute entries using 2800660 bytes of memory
>14718 BGP route-map cache entries using 235488 bytes of memory
>1712 BGP filter-list cache entries using 27392 bytes of memory
>178 received paths for inbound soft reconfiguration
>BGP activity 540738/474776 prefixes, 5007746/4847848 paths
>3037709 prefixes revised.
>
>and note - this is BINARY form...
>
>No, if someone want to implement the core BGP in the 8 MB ram, he can do
>it as well (through the cost of his work + cost of debug should be much
>greater than the cost of 128RAM memory -:)).
>
>Aleksei Roudnev, Network Operations Center, Relcom, Moscow
>(+7 095) 194-19-95 (Network Operations Center Hot Line),(+7 095) 230-41-41, 
>N 13729 (pager)
>(+7 095) 196-72-12 (Support), (+7 095) 194-33-28 (Fax)
>
>

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com




More information about the NANOG mailing list