2 ms·
NANOG presentation on using Anycast with TCP: http://www.nanog.org/meetings/nanog37/presentations/matt.levine.pdf http://www.nanog.org/meetings/nanog37/presenta
by peterwwillis 13y ago
NANOG presentation on using Anycast with TCP: http://www.nanog.org/meetings/nanog37/presentations/matt.levine.pdf http://www.nanog.org/meetings/nanog37/presentations/matt.lev... (tl;dr it works fine)
As far as CPU, there isn't a whole lot of cycles dedicated to decoding and replying to network packets, and serving static content is incredibly trivial. The interrupts from high loads of network traffic (usually small packets) are arguably the biggest impact on the CPU, which is why you get network cards that offload L3 processing much more efficiently than your CPU can. Network appliance vendors rely on them to help do things like transparently filter traffic on 40GB/s interfaces in real time, which would probably be impossible with a normal CPU.
They mentioned in a previous post that they mainly rely on L3 routing to load balance. And I don't remember if they specified this, but they hinted in the post that all customer traffic can be served by any frontend box; it just pulls the customer data from their main storage and caches it on frontends as needed, as any good proxy does.