summaryrefslogtreecommitdiffstats
path: root/dbus/test_server.cc
diff options
context:
space:
mode:
authorguoweis <guoweis@chromium.org>2015-11-01 14:05:43 -0800
committerCommit bot <commit-bot@chromium.org>2015-11-01 22:06:34 +0000
commitcd60d52ce5a94f47e966744245c3ca1567d49d85 (patch)
treee3b83ec19c09f8a72e160a2d147a1451f6e1db16 /dbus/test_server.cc
parent61b83e2ec049a9aa5343ff0072cdcae420d4943b (diff)
downloadchromium_src-cd60d52ce5a94f47e966744245c3ca1567d49d85.zip
chromium_src-cd60d52ce5a94f47e966744245c3ca1567d49d85.tar.gz
chromium_src-cd60d52ce5a94f47e966744245c3ca1567d49d85.tar.bz2
Create an experiment to study whether too many bindings cause NAT failure.
In this experiment, we're trying to study the impact to NAT by the number of bindings created in short intervals. The stunprober will send 1 ping to each server. There will be total |rounds| of probers. They will be grouped into batches. For example, we'll have the first N probers reporting the success rate of total recv over total send as the first batch, the next N as the 2nd batch. Each batch will report its own UMA. This way, we could observe whether the later batch has higher failure rate than the initial ones. The list of important parameters will be 1. the interval b/w the pings 2. the batch size 3. the total rounds This depends on ongoing CL https://codereview.webrtc.org/1422593002 BUG=549639 Review URL: https://codereview.chromium.org/1417663004 Cr-Commit-Position: refs/heads/master@{#357293}
Diffstat (limited to 'dbus/test_server.cc')
0 files changed, 0 insertions, 0 deletions