JMeter scalability on Internal Hardware

This page is just to clarify that the solution doesn't need the cloud and can be instigated
internally on hardware or VMs. This may broaden it's appeal to those projects where the
cloud is not appropriate, internal test environments or locked down firewalls for example.

If you supply a list of host ips in the jmeter-ec2.properties file, the controller will simply
use those hosts and not try to instantiate or tear down cloud boxes:

The controller script considers this setup when it comes to specific results files. If using
fixed hosts, it cleans up the /results directory before each test run. This is needed as these
files are not date stamped:

Something to consider here is other general clean up of your injectors in this case.
For example, the top level directory will build up a store of log files:
This solution has only been tested so far on Ubuntu 12.04.

[Home] [About (CV)] [Contact Us] [JMeter Cloud] [JM Highlights] [JM Overview] [JM Control] [JM Inject] [JM Threads]
[JM Results] [JM Assertions] [JM TPS] [JM Metrics] [JM Runtime] [JM Collation] [JM Logs] [JM 95th] [JM 95th v2] [JM Jenkins]
[JM Corporate] [JM Scripts] [JM Variables] [JM Embedded] [JM Hosts] [JM Running] [JM Example] [JM Versions] [webPageTest]
[_64 images] [asset moniitor] [Linux Monitor] [Splunk ETL] [Splunk API] [AWS bash] [LR Rules OK] [LR Slave] [LR CI Graphs]
[LoadRunner CI] [LR CI Variables] [LR Bamboo] [LR Methods] [LR CI BASH] [Bash methods] [Jenkins V2] [Streaming vid]
[How fast] [Finding Issues] [Reporting] [Hand over] [VB Scripts] [JMeter tips] [JMeter RAW] [Dynatrace] [Documents] [FAQ]
[Legal]
In the Cartesian Elements Ltd
group of companies