Hi Oliver- Like you, I've also built a load test harness that fires up independent copies of JMeter :)... it run on virtualized Redhat Linux ES on ESX server.
Whether you hit a problem with ESX depends on your tests, the ESX server hardware and how much memory and CPU you've allocated (or better 'reserved') for your test-runner system in ESX console. Based on your numbers, you won't much have a problem if the server is not already heavily laden doing other things for other people :) You can manage min. CPU and memory 'reservations' in ESX server console. I think we 'reserve' 4 GB RAM and 3GHz for each of the 2 CPU allocated to the VM. We run around 30 independent JMeter instances in parallel. Note, I had to reduce the JVM memory parameters each JMeter instance sets (by tweaking Jmeter.sh I think) to a more 'reasonable' level (made it around 1/4th - it depends on your tests though). The tests run with no display (using the JMeter '-n' (non-GUI) parameter). CPU usage isn't much and hits 20%. Network usage peaks at 5 Mbps during the testing. While its hard to put a precise number (due to ramp times, etc) my observations a while back showed upto 30,000 concurrent (running or sleeping) JMeter threads on that VM. One thing to watch out for - we hit problems due to NTP on VMWare not working very well. If the time goes backward JMeter gets confused and shows negative time for sampler requests etc. The solution was to use some sort of VMWare kernel module to bypass NTP and get time from ESX directly. Regards, Sonam Chauhan -----Original Message----- From: Oliver Erlewein [DATACOM] [mailto:[email protected]] Sent: Thursday, 26 February 2009 1:23 PM To: JMeter Users List Subject: Running JMeter virtualised instances Hi all, I'm being asked if I can run JMeter instances on a virtualised environment. The detail is that we (will) have massive machines (8 core lots of RAM) that will run VMware ESX server. On that I will need about 15-30 instances of JMeter running to generate the load needed. How does the virtualisation affect my results? In the past I've always run native as I don't trust virtualisation. JMeter will be the only service running. Has anyone done tests between native and virtualised? Any experiences? Pros / Cons? Any help is appreciated. Best Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] The information contained in this email and any attached files are strictly private and confidential. This email should be read by the intended addressee only. If the recipient of this message is not the intended addressee, please call Corporate Express Australia Limited on +61 2 9335 0555 or Corporate Express New Zealand Limited on +64 9 279 2555 and promptly delete this email and any attachments. The intended recipient of this email may only use, reproduce, disclose or distribute the information contained in this email and any attached files with Corporate Express' permission. If you are not the intended addressee, you are strictly prohibited from using, reproducing, disclosing or distributing the information contained in this email and any attached files. Corporate Express advises that this email and any attached files should be scanned to detect viruses. Corporate Express accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of any attached files. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
