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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 28: Line 28:


(Test client recommendations to be provided by Nick Hurley)
(Test client recommendations to be provided by Nick Hurley)
== Performance Tests ==
Test development is tracked in {{bug|728435}}.

Revision as of 22:58, 17 February 2012

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. The results of these tests will be pushed to a public graph server.

People

  • Nick Hurley (primary developer for NeckoNet) and Josh Aas will own the project.
  • Patrick McManus will work on developing the network profiles we test against.
  • Mozilla's automation team (including Clint Talbert and Dan Parsons) will help get servers, test automation, and graphing set up.

Schedule

We'd like to have something running with publicly displayed results during Q2 2012.

Infrastructure

Each NeckoNet proxy will run RHEL on its own low-power HP Blade 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.

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.

Supported NeckoNet Profiles

(Profiles to be provided by Patrick McManus)

Supported Test Client Configurations

(Test client recommendations to be provided by Nick Hurley)

Performance Tests

Test development is tracked in bug 728435.