[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Dual Homed BGP
- Subject: Dual Homed BGP
- From: mark.tinka at seacom.mu (Mark Tinka)
- Date: Sun, 16 Feb 2020 17:15:08 +0200
- In-reply-to: <CAAeewD-=Y92FOcDYLu=cWujC4fy3rXoo_jG=jAcGCf670Yk2Ww@mail.gmail.com>
- References: <CAASS9CTBrMQpw11QP1HaFK1_f+xcp3j4epWd6Ex=fmBdADFWrQ@mail.gmail.com> <CAPkb-7BLqGbXbPuzJjpbnN5pVPfTLcQjsQT8z11qu8pgsvKGvQ@mail.gmail.com> <[email protected]> <CAPkb-7BHMKazJ4ZNoYBgGYfAzbn9av4dSH5=aoQ9xfKJyX_Ygw@mail.gmail.com> <[email protected]> <CAAeewD-=Y92FOcDYLu=cWujC4fy3rXoo_jG=jAcGCf670Yk2Ww@mail.gmail.com>
On 16/Feb/20 16:51, Saku Ytti wrote:
> I'd really like to hear more datapoints from different eyeballs on this, like
>
> 60% local caches, of remaining traffic, 70% peered
>
> so transit = 0.4*0.3 = 12%
>
> I think this might be reasonable, but perhaps it's even less transit
> for eyeballs today?
So for us, we have quite a number of on-net caches, and the fill for
them (or origin pull) is typically done via peering.
Of the 85% we consider "peering traffic", around one-third of that is
traffic from our on-net caches.
Mark.