eCDN Stress Test Application

Overview

The eCDN Stress Test tool is aimed to deliberately and potentially intensely test the network by generating simulated traffic. Once the stress test is over, you will have all the information you need to prepare for the upcoming events.

How to Run a Test

  1. Download the application to a Windows machine.
  2. Install the application on a machine that has access to the network you want to test.
  3. Start broadcasting to an entry. This entry will be the entry that you will generate traffic to.
  4. Open the application and set the URL in the URL input field (see URL Formation) with the entry ID you are streaming to.
  5. Set the number of users you want to simulate. As a rule of thumb, one machine can generate up to hundreds of users. The exact number will differ on the installed hardware.
  6. Click Start.

Notes

  • The test tool is simulating video traffic and reports analytics to Kaltura, 
  • Delivery rules will work according to the stress test's IP (eCDN routing).
  • You can run multiple instances of the application on the same PC.
  • One needs to differentiate between the test network/PC's limits vs. KES limits. The test results may be affected negatively because of the PC limitation and not because of the network.

Installation

Please download latest version
https://pa-www.kaltura.com/content/static/downloads/eCDN.html

It's an windows application, no install needed
 

URL Formation

Option 1

https://<KES_HOSTNAME>/kAPI/cdnapisec.kaltura.com/p/<PARTNER_ID>/playManifest/entryId/<ENTRY_ID>/format/applehttp/protocol/http/a.m3u8

  1. Rename the KES hostname to the API gateway.
  2. Rename partnerId, entryId.
  3. Add ?ks=XXXXX if there is enforcement of KS for this partner.
  4. If there is a domain restriction,  if turned on,  choose a different access control profile.

Option 2

Run a curl for the playManifest and take on of the index-sXXXX.m3u8 files and add the kes hostname.

For example:

https://KES/kCache/klive.kaltura.com/dc-0/live/hls/p/XXX/e/YYY/sd/6000/t/ZZZ/index-s33.m3u8

How to Start CMD

usage --url [URL] --users [NUMBER]

What to Observe

  1. After you finish the stress test, two files are saved on the same directory where the application is located. The two files are:
    1. PlayerSimulator-access-XXX
      1. All the network details for the stress test. You would want to look in this file to see how long is took to download each ts.
      2. Stress Test Access-Logs Sample.xlsx
    2. PlayerSimulator-debug-XXX
      1. Verbose logs of the application
  2. Grep the access log the application produces (on the folder you are running it).
    Format of access: 
    [TIME] [SIMPLAYERID] [URL] [RESPONSE SIZE] [TIME TO DOWNLOAD] [KES CACHE HEADER] [ERROR STRING]  
  3. In the UI, you can see how many chunks and manifests have been downloaded.  
  4. While the test is taking place, it is recommended to go to the eCDN Monitoring Dashboard to view the system performance, since the Stress Test application is essentially generating traffic from players that send all the analytics events,  thus allowing you to monitor eCDN Monitoring Dashboard.
  5. As a rule of thumb: If the Max avg chunk/manifest is above 5 seconds then there is a need to revisit the eCDN setup.
  6. The expected result is: 1.5 max, avg of 300 ms, with a small standard of deviation.
In This Article
Was this article helpful?
Thank you for your feedback!