...
- Wants guidelines for scheduling test. Primarily test with your peers but some things related to own backbone.
- How long should test run?
- Joe: it shouldn't be 10% of utilization and 10% seems high
- There is not good way to know when people are testing, but BWTCL does have a way to control how much testing is done to you - one of main purposes
- Jeff: During early Internet2 days decided on fix % based on capacity. It was 10% but at time were very overprovisioned.
- Jeff and Chris Small: In early days of Internet2, BWCTL was sometimes in 30%-50% range of utilization.
- Chris Small: Currently most of IPV6 traffic is measurement
- Joe: Anyone have issue with that?
- Tom: Traffic cyclical so doing % over a period of time can be tricky given this fact.
- Jeff: If you're over-provisioned then doesn't matter, but once you start hitting congestion you want to back off tests
- Martin: Can do heavyweight that tell user you can get X performance, and do smaller ones to track heavy one without problem.
- Group: Is one week enough for heavyweight and 4-6 times for lightweight?
- Tom: Interval needs to relate to what users is doing.
- Jeff: Once a week does not seem like enough because config changes happen more than that.
- Martin: Might depnd on your network
- Vangelis: Do want to test to everyone (i.e. n-squared)?
- Jeff: No
- Jeff: You start running out of timeslots between 15 and 20 hosts if you're doing hourly because tests take time.
- Carla: would it make sense to make to create a document that has guidelines?
- General consensus was yes
- Carla: should share with NTAC for awareness
- Group: Version of NPToolkit released tomorrow supports that
- Martin: Can do it manually now but show also automate it in the future. We need more thought into how we will do that.
- Joe: How often you run tests, should that be related to who you are sending them to? i.e. send them more to people who are closer since it could have bigger impact.
- Jeff: You still have to run them a fair amount of time
- Brian: Too close is not useful either though
- Joe: I would guess that people will test with 6-12 sites
- Joe: Anyone who sets-up should setup DNS and preferably set up DNS with location records. Helps with visualization.
- Joe: QOS is set on ESnet as scavenger so if "real" traffic starts then measurement traffic is the first to go
- Brian: Should heavyweight have no QOS since it needs to tell you what you can get.
- Jeff: Depends on what you're after.
- Joe: In terms of scheduling tests Eli Dart has pushed the idea that we should define what a reasonable rate for the standard user is. Use that number for the tests.
- Rich: What about science community that needs more?
- Joe: They invest more in making performance better. That's minority of sites though and we want to tell the 95% of sites that don't have CMS or ATLAS data
- Rich: Do you want to set the bar higher so they can reach for it?
- Joe: We want to let them know there is a bar.
- Danno: What's the difference between butting up a web page is this is what you can get vs a page on how to tune system
- Jeff: Wondering how you are going to limit your tests to a certain amount.
- Jeff: It would be good to be able to show that 90% of sites get better perfomance than you, there must be something wrong
- Brian: It would be useful for NPToolkit to generate email alerts if BWTCL tests don't reach a threshold
- Joe: What should be X% capacity and Y% utilization for measurement tests be?
- Jeff; Depends on a lot of stuff. Three cases:
...