Skip to main content Skip to complementary content

Stress testing on AWS Auto-Scaling Group instance

In this section, you will simulate the situation like sudden/planned increased web service requests traffic (E.g. during sales event) and your Runtime instance will be running at 80% CPU utilization.

To do so, you will run a small stress testing script on the new Talend Runtime instance created from above.

Procedure

  1. SSH log in into the Talend Runtime EC2 instance running from initial launching step.
  2. Download “stress” rpm using the following command: 
    wget ftp://fr2.rpmfind.net/linux/dag/redhat/el7/en/x86_64/dag/RPMS/stress-1.0.2-1.el7.rf.x86_64.rpm
  3. Install “stress” locally as shown below. 
    yum localinstall stress-1.0.2-1.el7.rf.x86_64.rpm
  4. Once “stress” installed, run the command as shown below to burn CPU utilization at 80% (at least for 5 minutes). 
    stress –cpu 80
  5. Login into Talend Administration Center GUI/Servers page, you may observe that the Talend Runtime EC2 instance is showing very high CPU utilization.
  6. Observe in AWS EC2 services page, you can see a new TalendRuntimeAutoScaling instance has been started by AWS Auto-Scaling as shown below:
  7. Once the new Talend Runtime finished initialisation, you may observe this new instance already registered into Talend Administration Center/Servers and the testREST service Job also deployed in Talend Administration Center/ESB Conductor page.
  8. You may also test your deployed testREST service by using the AWS Load Balancer address. You can see the host addresses returned here are from different Talend Runtime instances at backend.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here