Networking/Archive/Necko/Performance/AutomatedTesting: Difference between revisions

Networking/Archive/Necko/Performance/AutomatedTesting (view source)

443 bytes removed , 18 September 2012

no edit summary

Confirmed users, Bureaucrats and Sysops emeriti

1,680

edits

@@ Line 3: / Line 3: @@
 == Summary ==
-The goal of this project (Stone Ridge) is to develop a system that can run automated performance tests every day against different network conditions, simulated by [[NeckoNet|NeckoNet]]. The results of these tests will be pushed to a public graph server.
+The goal of this project (Stone Ridge) is to develop a system that can run automated performance tests every day against different network conditions, simulated by [[NeckoNet|NeckoNet]]. The results of these tests are pushed to a public graph server.
 == People ==
@@ Line 40: / Line 40: @@
 In all cases the bandwidth should be shared across all IPs. I didn't model loss here, even tough it can be an issue, because its randomness would introduce way too much variability into short tests. As a separate effort we could build tests with deterministic loss.
-== Supported Test Client Configurations ==
-For starters, we will have
-* One RHEL 6, 64-bit
-* One Windows 7 Professional, 64-bit
-On the server side, there are three (3) RHEL 6, 64-bit machines, each providing a network under the conditions listed above. One of these also doubles as the "master", which talks to the outside world for things like downloading builds of firefox and reporting results from all clients to the graph server.
 == Performance Tests ==
 Test development is tracked in {{bug|728435}}.