Unleash Your Cloud Load Stress Monster
The Cloud Zone is brought to you in partnership with Mendix. Better understand the aPaaS landscape and how the right platform can accelerate your software delivery cadence and capacity with the Gartner 2015 Magic Quadrant for Enterprise Application Platform as a Service.
Location. Location. Location.
You may have the following options:
- Buying a lot of hardware and setup a one time (or more) lab and check your system capabilities. Pros: its your own servers and you will always find something to do with these extra servers. Cons: It will burn your budget, keep your staff night and days to setup it and will require several days to months to get all installed.
- Rent a lab and do your things there: Pros: You really don't need to put that amount of money Cons: Schedule the lab, making sure that the hardware and networking meet your needs, making sure software licenses are available... Most important, if you find a major issues in the first day, you will have to close the lab and reschedule another test (and pay again).
- Setup a cloud based lab. Pros: No setup fees, no need to schedule, no need to commit, and you can save your environment, shut it down, and turn it on when you will need it again. Cons: You don't really own the servers, but hey, who really wants to own servers?
OK, so we chose the cloud again. What about the tools? should we choose HP Software LoadRunner or Radview WebLOAD? If so get ready to write a 6 digits number check.
However, the smart choice is selecting the open source tool: Apache JMeter, that can generate HTTP stress (it's a world wide web world after all) at the price of $0. This tool requires you to build the stress scripts in a manual manner using drag and drop, parameters configuration and BASH scripts and it supports visualization using graphs and reports (it also support SOAP, HTTPS, LDAP, JMS, IMAP, JDBC...)
One last thing, JMeter support "bot network" mode, where several JMeter instances can load a single system and provide a unified reporting.
Decisions. Decisions. Decisions.
So we chosen the cloud environment (Amazon AWS currently provides the best offer) and JMeter... now just before launching instances, lets make several decisions that will help us keep costs as low as possible.
Getting Best Prices
- Windows or Linux: since JMeter is Java based, it's platform independent and Linux will be the smart choice.
- Spot prices: by using spot request, you can save about 60% of your CPU cost, and 30% of the total cost.
- Install both stress loaders and the system in Amazon to avoid paying for traffic.
Stop talking. Start Working.
Lets start with several basic steps:
- Download Client Tools that will be used to connect using SSH from Windows host :
- Sign up to Amazon AWS and prepare your user:
- Sign up
- Gen a KeyPair from the AWS management console (can be done using CLI if you prefer so).
- Download the KeyPair (PEM file) and create
a private key (PPK file) that can be used by Putty and WinSCP:
- Open PuttyGen
- Conversions > Import Key to import your .PEM file
- Click on "Save private key" to create your private key file (PPK)
- Launch your instance and connect to it
- Launch an image from EBS based image (if you prefer to keep your work for next time). Use spot request to save some money. Please notice that the default Linux flavor is Fedura.
- Connect using WinSCP and the PPK file. CLI should be done by starting Putty from within the WinSCP.
- Install JMeter and its dependencies:
- Download and install JMeter
- Download the JMeter tar file from the site using wget
- Unzip the file using tar -zxvf file.tar.gz
- Download and install Java
- Download java using wget from http://java.com/en/download/manual.jsp and install it
- Set X permissions on the Java: chmod a+x jre-6u-linux-i586.bin
- Run jre-6u18-linux-i586.bin to install Java
- Set environment variables:
- Set Path: PATH=$PATH:/etc/java/jre1.6.0_18/bin (update it according to path where you installed Java).
- Set Path: PATH=$PATH:./
- Download and install JMeter
- Launch your JMeter
- jmeter -n -t my_test.jmx -l log.jtl
- You may find full details of this syntax in the Apache
Jakarta JMeter page:
- -n: nongui mode
- -t: the script file you built before
- -l: the results file
Finally we a stress lab in the cloud, all that left is writing your stress script, installing your system and start stressing it...