Changes between Version 2 and Version 3 of PerformanceTesting

Timestamp:

09/26/11 08:41:52 (13 years ago)

Author:

Samuli Seppänen

Comment:

--

PerformanceTesting

@@ +1 @@
+[[TOC(inline, depth=1)]]
+
 = Introduction =
 
-There have been significant changes in the future 2.3 branch since the relatively stable and conservative 2.1.x and 2.2.x releases. Therefore there's a definite need for wide testing in various areas, including performance. This page tries to outline what the most relevant tests are so that they can be ran on a regular basis during development to spot any regressions and bottlenecks. These tests are primarily aimed at the future OpenVPN 2.3 branch (current "master"). However, same setup can used to test older versions, too. Focus is on testing the most common configurations. If possible, potential bottlenecks are identified beforehand and tests focused there.
+There have been significant changes in the future 2.3 branch since the relatively stable and conservative 2.1.x and 2.2.x releases. Therefore there's a definite need for wide testing in various areas, including performance. This page tries to outline what the most relevant tests are so that they can be ran on a regular basis during development to spot any regressions and bottlenecks. These tests are primarily aimed at the future OpenVPN 2.3 branch (current "master"). However, same setup can used to test older versions, too. Focus is on testing the most common and/or potentially useful configurations, as testing all combinations is practically impossible. 
+
+= Goals =
 
 The tests have several goals:
@@ -59 +63 @@
  * Other questions, which?
 
-= Test environments =
+= Test environment =
 
 == General considerations ==
@@ -67 +71 @@
 == Amazon EC2 ==
 
-Amazon EC2 is used for maximum simultaneous connection testing, where a large number of clients is required. It can also be used for throughput tests, provided that the server and clients are in the same availability zone (to reduce unnecessary costs.
+Amazon EC2 is used for maximum simultaneous connection testing, where a large number of clients is required. It can also be used for throughput tests, provided that the server and clients are in the same availability zone (to reduce unnecessary costs).
 
-Test environment setup is handled by the Python deployment tool that utilizes Fabric under the hood(FIXME: add link).
+Test environment setup is handled by the Python deployment tool (see below) that utilizes Fabric under the hood.
 
 == Local (LAN) ==
@@ -75 +79 @@
 LAN environment is/can be used for throughput tests. Server and clients are connected to a high-quality, high-bandwidth switch to avoid forming external bottlenecks.
 
-Test environment setup is handled by the Python deployment tool that utilizes Fabric under the hood. Initial installation of client OSes is automated using FAE (Debian) or Kickstart (RHEL/Fedora derivative.
+Test environment setup is handled by the Python deployment tool that utilizes Fabric under the hood. Initial installation of client OSes is automated using FAE (Debian) or Kickstart (RHEL/Fedora derivatives).
 
 == Configuring test server(s) ==
@@ -83 +87 @@
 The required steps:
 
- * Install precompiled OpenVPN binary and shared libraries
- * Install an OpenVPN configuration file
-  * Repeat for all chosen configuration
+ * Install a precompiled OpenVPN binary and shared libraries
+ * Install an OpenVPN configuration file (for every configuration to test)
  * Start OpenVPN
  * Start memory/CPU usage monitoring tools
@@ -107 +110 @@
   * Wait until the test is over
   * Cleans up system state:
-   * Kill OpenVPN gracefully; should it fail, makes note of it and uses ''kill -9''
+   * Kill OpenVPN gracefully; should it fail, make note of it and use ''kill -9''
    * Flush routes
   * Push collected data into a centralized location (e.g. using SSH)
- * Install crontab entry for each test scenario
-   * Launches a test script at a given time
+ * Install crontab entry for each test scenario to launch a test script at a given time
 
 = Tools =