Mesh Testing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
This page describes the network testing that will be performed on Monday Feb 25th at 1cc. |
This page describes the network testing that will be performed on Monday Feb 25th at 1cc. |
||
Setup: |
|||
* Start with ten machines, keep adding ten until data doesn't change. |
|||
Measurements to make during each test: |
Measurements to make during each test: |
Revision as of 21:09, 21 February 2008
This page describes the network testing that will be performed on Monday Feb 25th at 1cc.
Setup:
- Start with ten machines, keep adding ten until data doesn't change.
Measurements to make during each test:
- Spectrum utilization -- estimate rate, integral, vs. idle
- Remaining bandwidth -- attempt to download a large file on one machine during test, record time taken.
- Total # of laptops seen on mesh view on all numbers (should be n^2).
Workloads -- tests to perform, along with their quantitative metrics:
- Idle load.
- Every machine coming out of suspend.
- Every machine trying to register with school server -- Number of machines that failed the first attempt, failed second attempt, etc.
- Ricardo's web spider -- record rates
- Read -- if one laptop shares a PDF, how many laptops fail to retrieve it?
- Distance
- Write -- automate pressing 1 character every second, look at received rate/update time, increase number of participants
- olpc-update -- number of machines upgraded in 1 hour
Variables to investigate:
- Set mesh ttl to 1 for every packet
- Change bcast/mcast rate on every node
- Jim's Avahi config 30% fix?
- Presence: Benchmark bandwidth use of Avahi vs. Cerebro vs. no presence?
- Collaboration: Benchmark switching from multicast to unicast?
- Suspend/resume: Off vs. on, wake-on-unicast vs. wake-on-multicast