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

← Older edit

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

Revision as of 09:00, 24 April 2023

262 bytes added , 24 April 2023

m

Manuel Bucher moved page Necko/Performance/AutomatedTesting to Networking/Archive/Necko/Performance/AutomatedTesting: move to necko archive

Manuel Bucher

210

edits

@@ Line 1: / Line 1: @@
+{{Template:Archived}}
+= WARNING WARNING WARNING - READ FIRST =
+Both Stone Ridge and NeckoNet are obsolete and no longer maintained. This information exists here for historical purposes only.
 = Automated Performance Testing w/NeckoNet (Stone Ridge) =
 == 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 18: / Line 24: @@
 == Results ==
-Results are reported [https://datazilla.mozilla.org/stoneridge/ here].
+[https://datazilla.mozilla.org/stoneridge/ Results are reported here]. Note: for now you must select a Firefox >=18 in the "Control Panel" to see results.
 == Infrastructure ==
-Each NeckoNet proxy will run RHEL on its own low-power HP server. NeckoNet proxies will not run in VMs so as to avoid potential network interference from a VM hypervisor. The NeckoNet proxy will not have an internet connection for security purposes. We are originally planning to deploy three NeckoNet proxies.
+We currently have three NeckoNet servers. All are HP servers running RHEL 6.2. NeckoNet servers do not run in VMs so as to avoid potential network interference from a VM hypervisor. The servers have dual NICs, one for our private test network and one to the outside network. One server doubles as the "master", which handles tasks such as downloading Firefox builds and reporting results from all clients to the graph server.
-Test client machines can run any OS and may be VMs. These machines will be configured to run tests against the NeckoNet proxies and report results to a graph server. Test clients will also not have connections to the internet for security purposes.
+We currently have three test client machines - one OS X 10.8, one RHEL 6.2, and one Window 7.
+These machines are configured to run tests against the NeckoNet servers and report results to a graph server. Test clients also have two NICs, one for our private test network and one to the outside network.
 == Supported NeckoNet Profiles ==
@@ Line 39: / Line 47: @@
 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 ==
+== Performance Tests ==
-For starters, we will have
+Test development is tracked in {{bug|728435}}.
-* One RHEL 6, 64-bit
+== To-Do List ==
-* 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.
+# Get OS X test client reporting results.
+# Ability to push custom builds for performance testing.
-== Performance Tests ==
+# Write more tests.
+# Add TLS/OCSP testing capabilities.
-Test development is tracked in {{bug|728435}}.
+# Add ability to measure impact on pageload in addition to network-level results.