Beware of under networked cloud environments. It's one of the components that doesn't virtualize well and ti will affect reported results and ability to apply a consistent load.
Regards, Kirk On Jun 24, 2011, at 12:45 AM, Oliver Lloyd wrote: > Will, The fact is, running JMeter in the Cloud is easy! In practical terms > it's no different from running it using a bunch of PCs sitting on your > desktop. But, 'The Cloud' as a phrase is somehow...exciting? It is pretty > cool, no doubt, but really, it's just hardware, hardware that is connected > together using a private network that you access via a larger network which > is called the internet. It's exactly the same as having a bunch of PCs on > your desk that you've connected together using a little router and then > having that plugged into your corporate LAN - same, same, except one is > slightly bigger... > > But you need to learn a few skills. You'll come up against various issues > and each of them will have a solution posted somewhere on the internet - > some of them will be frustrating and hard to find, some will take ages, but > by going through this pain you actually learn a lot - you'll become better > by doing it. Give a man a fish and all that. > > It took me about two weekends to figure it all out. I started, like you, > looking for the guiding light, that one blog post that would give me all the > answers, but it's not out there. Instead I found a patchwork of individual > pieces of information that added together to form the solution that was > right for me. > > Each of the points you raise are little mini subjects in themselves and > there is a lot of stuff out there about them so...dig. > > But, all that said, here's some (Amazon specific) tips: > > Think Java. This is your priority when building an AMI. > Build AMIs from scratch, use virgin distros and install only what you need. > Keep all of the rig in the cloud; don't try to run it using your local > machine as a master. > Connect internally using the internal addresses, not the public IPs or > public hostnames. > Go 64 bit. > Experiment using micro instances but run real tests on large. > Learn how to use CloudWatch. Then use it! > Keep building new AMIs, perfect these. > Maintain a replica data structure on your local machine and develop here. > Learn SCP. > Become a master in SSH. > Think lean, think mean. ( > http://jakarta.apache.org/jmeter/usermanual/best-practices.html#lean_mean > lean and mean ) > Use linux for your AMIs AND locally. > Use linux locally. > Use Linux! > Don't fret over cost, it's cheap. Period. > Play, experiment, run tests, build and tear down instances willy nilly. > Create a security group and configure it to open up all your instances to > each other - using INTERNAL addresses. > If you are lazy, use elastic IPs, but you don't need them. > > Above all, have a good reason to use the cloud. Too many people think it's a > solve-all solution for all performance testing needs. It's not. You CANNOT > safely use external hardware to pump traffic into your corporate network. > This will not allow isolated testing, will introduce uncontrolled variables, > and could potentially bring your comapny network down, beware. > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/best-practices-for-jmeter-on-amazon-ec2-aws-cloud-tp4517881p4519296.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
