{"id":22447,"date":"2015-07-15T22:14:55","date_gmt":"2015-07-15T16:44:55","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=22447"},"modified":"2015-09-14T05:36:55","modified_gmt":"2015-09-14T00:06:55","slug":"master-slave-load-testing-using-aws-ec2-spot-instances","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/master-slave-load-testing-using-aws-ec2-spot-instances\/","title":{"rendered":"MASTER-SLAVE LOAD TESTING USING AWS EC2 SPOT INSTANCES"},"content":{"rendered":"

Load testing using JMeter from a single server generally yields the inaccurate result which doesn\u2019t meet the real-time scenario. When performing load test from a single server<\/a>, there are some network bottlenecks which restrict JMeter to perform an accurate load test. If the number of users exceeds a limit, the network starts getting choked up leading to an incorrect result. It is always better to perform load test from different sites by sending concurrent users to your application which not only brings the level of accuracy to your load test but also give flexibility to check the performance of your web application in real time scenario.<\/p>\n

 <\/p>\n

Use case<\/b><\/p>\n

When we perform load test using EC2 servers<\/a>, we need to pay the full hour cost of the servers in spite of knowing that our load test will take less than an hour. When it comes to the master-slave setup of load testing, you might be needing 5-10 slave servers to perform an efficient load test. This problem can be solved by using the spot instances which can be available to you in 60-70% lesser cost than a previous one. Spot instances in this scenario will fit best in the picture because it doesn\u2019t matter if one of your slave instances got terminated due to high pricing, you can start your load test again with an ease. In this blog, I will be demonstrating how we can perform distributed load testing using master-slave setup in the same subnet of a VPC.<\/p>\n

 <\/p>\n

Master-Slave Jmeter Load Testing<\/b><\/p>\n

In Master-Slave JMeter load testing, one instance behaves like a master (generally a small-sized \u00a0instance) and multiple high-performance servers behave like slave servers. Slave servers actually perform the load test by sending requests on to the web application. The master server triggers the load test job and gives aggregated output in XML format which can further be converted into HTML format using Apache Ant tool.<\/p>\n

 <\/p>\n

Below is a bash script which will set up the master-slave configuration using spot- instances in a single public subnet.<\/b><\/p>\n

Prerequisites:-
\n<\/strong>1. Load testing \u00a0JMX file
\n2. Apache Ant configured Master Server.
\n3. AWS-CLI
\n4. A build.xml for Apache Ant, required to present in the target directory of JMeter to view the result in a web browser after converting the result from XML to HTML.<\/p>\n

 <\/p>\n

Script Overview:-<\/b><\/p>\n

The script will perform following tasks step by step after being run from master JMeter server:-<\/p>\n

    \n
  1. Choosing the number and type of slave servers.<\/li>\n
  2. Bidding of slave servers by showing you the last hour pricing of the instances in all the Availability zones.<\/li>\n
  3. Configuring JMeter on slave servers and preparing them for ready to use.<\/li>\n
  4. Performing load test in a master-slave configuration.<\/li>\n
  5. Giving XML output of the load test.<\/li>\n<\/ol>\n

     <\/p>\n

    Below is a script named \u201cuser_data_for_loadtesting.sh\u201d which will be passed as a user data to the slave servers when the spot requests will be accepted. The script will install JMeter in the slave servers and make them ready to use by running the script JMeter server.<\/b><\/strong><\/p>\n

    [js]
    \n#!\/bin\/bash
    \n \tsudo apt-get update
    \n \tsudo apt-get install jmeter -y
    \n\t\tsudo sed -i ‘s\/remote_hosts=127\/#remote_hosts=127\/’ \/usr\/share\/jmeter\/bin\/jmeter.properties
    \n\t\tsudo \/usr\/share\/jmeter\/bin\/jmeter-server
    \n[\/js]<\/p>\n

    Below is the main script named \u201cperform_load_test.sh\u201d to perform the whole task.<\/b><\/p>\n

    [js]
    \n#!\/bin\/bash
    \n current_date=`date +%Y-%m-%dT%H:%M:%S`
    \n hour_ago_date=$(date +%Y-%m-%dT%H:%M:%S -d "1hour ago")
    \n echo "= + = + = + = +WELCOME TO AUTOMATED LOAD TEST USING SPOT INSTANCES= + = + = +"
    \n echo "choose instance type:"
    \n echo "1.m3.medium"
    \n echo "2.m3.large"
    \n echo "enter choice:"
    \n read ch
    \n case $ch in
    \n 1) instance_type=m3.medium;;
    \n 2) instance_type=m3.large;;
    \n *) invalid option;;
    \n esac<\/p>\n

    echo "SPOT PRICE HISTORY FOR $instance_type IN LAST HOUR IS :- "
    \n aws ec2 describe-spot-price-history –region us-east-1 –instance-types m3.medium –filters Name="product-description",Values="Linux\/UNIX" –start-time $hour_ago_date –end-time $current_date –query ‘SpotPriceHistory[].[AvailabilityZone,SpotPrice]’ –output text | tail -n 4<\/p>\n

    echo "enter your spot price::"
    \n read price
    \n#Here is a need to encode the userdata script in base64 format to pass it as a user data.<\/p>\n

    userdata_encoded_slave="$(cat ~\/user_data_for_loadtesting.sh | base64 -w 0)"<\/p>\n

    echo "enter no. of slave instances required:: "
    \n read number
    \n req_id=($(aws ec2 request-spot-instances –region us-east-1 –spot-price $price –launch-specification "{ \\"KeyName\\": \\"kew\\", \\"ImageId\\": \\"ami-d05e75b8\\" , \\"InstanceType\\": \\"m3.medium\\" , \\"UserData\\": \\"$userdata_encoded_slave\\" , \\"SecurityGroupIds\\": [\\"sg-8b451aef\\"] }" –query ‘SpotInstanceRequests[].SpotInstanceRequestId’ –output text –instance-count $number))<\/p>\n

    for r in "${req_id[@]}"
    \n do
    \n aws ec2 describe-spot-instance-requests –spot-instance-request-ids $r –query ‘SpotInstanceRequests[].[SpotInstanceRequestId,State]’ –output text | grep active
    \n status=$?
    \n while [ $status -ne 0 ]
    \n do
    \n echo "Checking for approval..Please wait"
    \n sleep 8
    \n aws ec2 describe-spot-instance-requests –spot-instance-request-ids $req_id –query ‘SpotInstanceRequests[].[SpotInstanceRequestId,State]’ –output text | grep active
    \n status=$?
    \n done<\/p>\n

    echo "************! ! ! ! ! ! CONGRATULATIONS !!!!….YOUR REQUEST HAS BEEN ACCEPTED !!!!!!!!*************************"<\/p>\n

    inst_id=`aws ec2 describe-spot-instance-requests –spot-instance-request-ids $r –query ‘SpotInstanceRequests[].InstanceId’ –output text`<\/p>\n

    ip=`aws ec2 describe-instances –instance-ids $inst_id –query ‘Reservations[].Instances[].NetworkInterfaces[].Association[].PublicIp[]’ –output text`<\/p>\n

    echo "The IP of allocated instance is :- $ip"
    \n r_ips=$r_ips,$ip #formatting for jmeter command to pass remote IPs
    \n done
    \n remote_ips=`echo $r_ips | sed -e ‘s\/,\/\/’`
    \n sudo sed -i ‘s\/remote_hosts=127\/#remote_hosts=127\/’ \/usr\/share\/jmeter\/bin\/jmeter.properties
    \n echo "Performing load testing ……..Please wait"
    \n echo "Initializing Remote host..Please wait.."
    \n sleep 210
    \n #to perform load test in master slave, the command is
    \n #jmeter -n -t <jmx file> -l <result.xml> -R xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx (remote hosts)
    \n jmeter -n -t \/home\/ubuntu\/<jmx-file.jmx> -l \/home\/ubuntu\/result.xml -R $remote_ips
    \n[\/js]<\/p>\n

    In the end, you will get an XML file named result.xml which can easily be converted in HTML format using Ant Apache tool or some other tool.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Load testing using JMeter from a single server generally yields the inaccurate result which doesn\u2019t meet the real-time scenario. When performing load test from a single server, there are some network bottlenecks which restrict JMeter to perform an accurate load test. If the number of users exceeds a limit, the network starts getting choked up […]<\/p>\n","protected":false},"author":170,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":19},"categories":[1174],"tags":[1950,1952,696,1948,1951,1949],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/22447"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/170"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=22447"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/22447\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=22447"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=22447"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=22447"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}