AISM Platform Load Test For SCU4 with DI PoC


test run parameters:



The process:

Devices are simulated using headless browsers running on a cisco blade center. Each browser is run in a container with its own MAC address and DHCP-retrieved IP address. The containers are created and perform dhcp prior to the test. (This process is not included in the results.)

One headless browser is started every 2 seconds. After 100 browsers have been started, a delay of 10 seconds is inserted to provide a short amount of time for the system to recover from some of the load. (There is a balance here in simulating enough load in a short period of time to be useful, but not overloading the server with an entirely unrealistic situation.)

Each headless browser:

  1. Tries to talk to the web
  2. Gets captured and redirected to the DI portal
  3. Sends some traffic to the DI portal
  4. Triggers pax-wait
  5. 'Purchases' on the ground ISP page
  6. Loads an 'idle' page from the internet that cycles between 2 large non-cachable images (of cats, of course) in order to create some data flow.
  7. Stays on the above page for a while. Then it stops that page and will hit the idle-timeout some time later.

This load test run is right on the edge of failing. With a delay of 2 seconds between passenger device 'kick off', we see a 93% success rate. (If we drop that delay to 1 second, we see mass failure. If we increase the delay to 3 seconds we see 100% success.) Given that this is an un-optimized prototype system, and we have 600 passenger devices represented, we feel comfortable that the final integrated system should support the passenger loads expected on KAL.



* Values of -1 are an indication of an SNMP read error.