Performance of a DHT Implementation in the BRN Indoor Testbed: Difference between revisions

From
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
== Objectives ==

* Evaluate performance and scalability of the DHT implementation (Latency, Bandwith, Startup latency, Changes in the network structure)
* Comparation between DHT and traditional approaches (Flooding)
** Difference in fulfilling a request
** Difference in startup latency
* Comparation between simulation and experimental results

== Measurement Plan ==
== Measurement Plan ==

=== Influence Factors ===

* Size of the (core BRN) network in number of nodes
* Number of clients (TODO absolute or per BRN node)
* Changes in the network structure
* TODO Charater of requests?
* TODO Amount of stored data (number of DHT keys)?

=== Measurement Values ===

* Response time of an request (DHT/ARP/DHCP)
* Used bandwidth for fulfilling a request (number of packets or bytes?)

=== Constants during Measurement ===

* Only 1 request at a time

=== Measurement: Latency ===

* Variable number of nodes n
* Only on client
* Measure time for fulfilling a request for DHT and Flooding

=== Measurement: Bandwidth ===

=== Measurement: Startup Latency ===

=== Measurement: Dynamic Changes in the Structure of the Network===

* Measure time for reorganization

== Measurement Setup ==

== Results ==

Revision as of 10:01, 27 January 2006

Objectives

  • Evaluate performance and scalability of the DHT implementation (Latency, Bandwith, Startup latency, Changes in the network structure)
  • Comparation between DHT and traditional approaches (Flooding)
    • Difference in fulfilling a request
    • Difference in startup latency
  • Comparation between simulation and experimental results

Measurement Plan

Influence Factors

  • Size of the (core BRN) network in number of nodes
  • Number of clients (TODO absolute or per BRN node)
  • Changes in the network structure
  • TODO Charater of requests?
  • TODO Amount of stored data (number of DHT keys)?

Measurement Values

  • Response time of an request (DHT/ARP/DHCP)
  • Used bandwidth for fulfilling a request (number of packets or bytes?)

Constants during Measurement

  • Only 1 request at a time

Measurement: Latency

  • Variable number of nodes n
  • Only on client
  • Measure time for fulfilling a request for DHT and Flooding

Measurement: Bandwidth

Measurement: Startup Latency

Measurement: Dynamic Changes in the Structure of the Network

  • Measure time for reorganization

Measurement Setup

Results