NFD

This is the report for the NFD forwarding benchmark.

The tests were running over ONL (https://onl.wustl.edu/). John's script (https://github.com/WU-ARL/NFD_Performance_Testing_on_ONL.git) is modified to manage the tests.

The latest NFD and NDN-cxx library were used in the tests. They were built with the standard default compilation options.

I. Experiments:

The tests were run with 128 client all routing through one central nfd router. Two scenarios are provided: content provided, and no content provided.

In each of the scenarios, three different name length are used. Note that 128 different base names were given: end of name ranged from 000 to 127.

1. Short: /abcde/000

2. Medium: /abcde/fghij/klmno/pqrst/125

3. Long: /abcde/fghij/klmno/pqrst/uvwxy/zabcd/efghi/jklmn/opqrs/tuvwx/yzabc/defgh/ijklm/nopqr/stuvw/xyzab/cdefg/hijkl/mnopq/rstuv/wxyza/bcdef/ghijk/lmnop/qrstu/127

A sequence number is appended by ndn-traffic to each Interest to force every name to be unique.

II. Results:

A. Approximate rate nfd was able to handle:

1. Short:
   With content provided: 4800 Interests/s
   W/o content provided: 14800 Interests/s

2. Medium:
   With content provided: 3500 Interests/s
   W/o content provided: 10000 Interests/s

3. Long:
   With content provided: 1100 Interests/s
   W/o content provided: 2000 Interests/s

B. When the Interest send rate is below the threshold above, the loss rate is around 0.02%, which may be introduced when the test is killed.

C. Approximate latency for nfd:

1. Short: around 0.20ms

2. Medium: around 0.25ms

3. Long: > 0.6ms, sometimes around 1ms.

The tests parameters:

1. Name length: medium;
2. Contents are served;
3. Data payload size: 1435;
4. NFD version: latest
5. NDN-cxx version: latest

128 client-server pairs are used. 16 machines are for clients, and 16 machines are for servers (so each machine host 8 clients or 8 servers). Those machines are connected through a single NFD router. All the experiment machines are PC2core on ONL.

The results are the same:

1. Approximate latency for nfd is around 0.25ms;
2. Approximate rate nfd was able to handle is around 3500 Interests/s

This report describes the forwarding performance for the latest NFD released (v0.2).

The performance tests is running over ONL using the installed NFD.

The old reports have issues because the default compilation options are overridden when specifying the local ndn-cxx library directory using CXXFLAGS, which means there is no optimization.

The scripts for the tests is improved, so the manual to run the tests is uploaded again.

• I. Experiments:

  The tests were run with 64 client-server pairs all routing through one central nfd router. Two scenarios are provided: content provided, and no content provided.

  In each of the scenarios, three different name length are used. Note that 128 different base names were given: end of name ranged from 000 to 127.

  Short: /abcde/000

  Medium: /abcde/fghij/klmno/pqrst/uvwxy/125

  Long: /abcde/fghij/klmno/pqrst/uvwxy/zabcd/efghi/jklmn/opqrs/tuvwx/yzabc/defgh/ijklm/nopqr/stuvw/xyzab/cdefg/hijkl/mnopq/rstuv/wxyza/bcdef/ghijk/lmnop/qrstu/127

  A sequence number is appended by ndn-traffic to each Interest to force every name to be unique.

• II. Results:

  A. Approximate rate nfd was able to handle:

  Short: With content provided: 12000 Interests/s; W/o content provided: 40000 Interests/s

  Medium: With content provided: 10000 Interests/s; W/o content provided: 30000 Interests/s

  Long: With content provided: 4200 Interests/s; W/o content provided: 9600 Interests/s

The forwarding benchmark testing steps and report version 0.3 are uploaded. (They are conducted on the NFD v0.2.)
Please ignore the old reports.