Task #3482
open
Document expected packet processing performance
0%
Description
Publish expected packet processing performance (for example, packet processing delay v. throughput) for NFD releases installed on the testbed. Could the results of a set of standard performance tests, which may already exist, be published for each major NFD release, as well as minor releases expected to impact performance? Workloads of current interest for application team are NDN-RTC.
Updated by Junxiao Shi about 8 years ago
In short, what you see is what you get.
#1819 note-11 has some NFD 0.3 benchmark results on ONL, a controlled experiment network.
As a UCLA CS217A project, Akshay Vangari, et al also did some benchmarks across the testbed in 2014.
Updated by Jeff Burke about 8 years ago
Giovanni notes on 3/14: "from our first tests NFD with 1.5Kbyte packets runs at roughly 35Mbit/s on a I7 architecture and less than 10Mbit/s on an Atom Architecture."
Updated by Davide Pesavento about 8 years ago
Jeff Burke wrote:
Giovanni notes on 3/14: "from our first tests NFD with 1.5Kbyte packets runs at roughly 35Mbit/s on a I7 architecture and less than 10Mbit/s on an Atom Architecture."
More specifically, the i7 is actually an Intel Core i5-4200U @ 1.60GHz, while the Atom cpu model is N2600 @ 1.60GHz.
We did a very rough analysis with callgrind, and it looks like a significant fraction of cpu time is spent in Component::compare().
Updated by Davide Pesavento 6 months ago
- Tags set to documentation
- Category deleted (
Integration Tests) - Start date deleted (
02/28/2016)