210
edits
Networking/Archive/Necko/Performance/AutomatedTesting: Difference between revisions
Networking/Archive/Necko/Performance/AutomatedTesting (view source)
Revision as of 09:00, 24 April 2023
, 24 April 2023Manuel Bucher moved page Necko/Performance/AutomatedTesting to Networking/Archive/Necko/Performance/AutomatedTesting: move to necko archive
m (Manuel Bucher moved page Necko/Performance/AutomatedTesting to Networking/Archive/Necko/Performance/AutomatedTesting: move to necko archive) |
|||
| (17 intermediate revisions by 4 users not shown) | |||
| 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) = | = Automated Performance Testing w/NeckoNet (Stone Ridge) = | ||
== Summary == | == 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 | 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 == | == People == | ||
| Line 14: | Line 20: | ||
== Schedule == | == Schedule == | ||
We' | We'll be reporting results to a graph server from all three tier-1 platforms in Q3 2012. | ||
== Results == | |||
[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 == | == Infrastructure == | ||
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. | |||
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 == | == Supported NeckoNet Profiles == | ||
| Line 35: | 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. | 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. | ||
== | == Performance Tests == | ||
Test development is tracked in {{bug|728435}}. | |||
== | == To-Do List == | ||
# Get OS X test client reporting results. | |||
# Ability to push custom builds for performance testing. | |||
# Write more tests. | |||
# Add TLS/OCSP testing capabilities. | |||
# Add ability to measure impact on pageload in addition to network-level results. | |||