close Warning: Can't synchronize with repository "(default)" ("(default)" is not readable or not a Git repository.). Look in the Trac log for more information.

Changes between Version 1 and Version 2 of Internal/SystemPrototyping/Projects/RouterWorkload


Ignore:
Timestamp:
Dec 24, 2012, 8:51:15 AM (11 years ago)
Author:
aravind
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Internal/SystemPrototyping/Projects/RouterWorkload

    v1 v2  
    11= Router Workload =
     2
     3We want to design a MobilityFirst workload that can be used to test the performance of various MF router implementations, such as the CLICK software router, the OpenFlow based set up and the netFPGA router. The workload should have an appropriate distribution of traffic classes that will go through GNRS look up, storage etc. The arrival rate of the data itself can either be from a synthetic traffic generator or trace based.
     4
     5== Synthetic Traffic Generator ==
     6
     7A source that can generate MobilityFirst traffic with the traffic class distribution and arrival rate desired by the user. The following are some parameters of the traffic generator that can be tweaked by the user to control the traffic.
     81. Arrival rate of data/gap between chunks
     92. service ID distribution of the chunks - used to force a GNRS look up or storage
     103. chunk size ??
     11
     12== Trace Based Traffic Generator ==
     13
     14A real world trace is used to drive the traffic generator. Existing list of traces:
     151. [http://traces.cs.umass.edu/index.php/Network/Network YouTube request response]  trace from UMass.
     16
     17The arrival rate is determined by the time stamps in the trace file. However, the traffic class distribution should still be under the control of the user.