Intro: Systems and Protocols: Relation with Standards
IETF / Forces WG:
Data / Forwarding Plane
No awareness where things are
Awareness where things are
OSI Network Architecture DATA Application Pre. Session Transport Network Data Link Physical 7 6 5 4 3 2 1 DATA AH DATA PH DATA SH DATA TH DATA NH DATA DH DATA PH Application Pre. Session Transport Network Data Link Physical 7 6 5 4 3 2 1 Network Network A B
What is measured? Performance in packets per second versus a forwarding information base (FIB) that is increased in size.
Start application is IPv4.
Next, counters are added for per flow billing purposes.
Next, load balancing is introduced as an additional feature.
Finally, encryption becomes an additional requirement for 2% of the data that is being forwarded
Performance curves 10 20 30 50 100 150 FIB (K entries) Performance (Mpps) NPU B NPU A IPv4
Performance curves 10 20 30 50 100 150 FIB (K entries) Performance (Mpps) NPU B NPU A IPv4 + counters Requires more memory references
Performance curves 10 20 30 50 100 150 FIB (K entries) Performance (Mpps) NPU B NPU A IPv4 + counters + Load balancing Requires even more memory references
Performance curves 10 20 30 50 100 150 FIB (K entries) Performance (Mpps) NPU B NPU A IPv4 + counters + Load balancing + encryption No extra references and resources available A does not have sufficient resources
Architecture A Key extract LU Count Int. mem 3 MIPS cores Int. mem Int. mem External Buffer Mem Sched OC-192 POS OC-192 POS Hash IPv4 + counters + LB + crypto
Processor core metrics are not always relevant for networking applications
It might be relevant for NPU B, since functionality relies almost totally on those cores.
It is definitely not the case for NPU A, since there is extensive additional hardware support for specific functions.
GRANULARITY Highly granular specifications, data or benchmarking information can offer a wrongful picture of the actual performance capabilities of the DUT. Since Network Processing Devices are designed with specific applications in mind, benchmarks must exist for those specific applications
Combinations of applications or minor extensions have a completely different impact on both network processing devices
NPU A has a lot of well engineered hardware support that can offer additional services BUT fails almost completely when additional computing resources are required
NPU B is very ‘soft’; performance degrades slowly when additional services are requested and shows no abrupt peaks in the performance curves.
HEADROOM Benchmarks should combine applications as they occur in the real world to give a ‘sense’ of headroom that is available to support real world scenarios. It is however very hard to define a metric for headroom
CommBench – A Telecommunication Benchmark For NPs CommBench HPAs PPAs