| | 727 | Things to test. There are several things that can be tweaked, each with some type of consequence: |
| | 728 | 1. ''number of switches. '' Control packets and channels are tracked in terms of switches and controllers. More switches mean more state to track and save, each switch that detects a given event will generate its own set of event messages. |
| | 729 | 1. ''number of hosts. '' Unique host traffic is the prototypical trigger for message events. More hosts intuitively generate more events. |
| | 730 | 1. ''number of hops. '' A longer route to a particular service will add more network transport delays (propagation, queueing, kernel buffer etc). This makes for a potentially infrastructure-sensitive control plane. We use short, high-throughput links for our experiments. |
| | 731 | 1. ''number of services. '' More services (handlers) touching a certain event naturally incurs more processing overhead. |
| | 732 | |
| | 733 | Infrastructure. Hardware depends on what we get access to, but it is generally a quad or hex-core PC. All tests ore done using Ubuntu 12.04, since it is the de-facto platform for all of the software. |
| | 734 | |
| | 735 | |
