Real Time JMeter Properties Control with BlazeMeter

BlazeMeter's Real-Time JMeter Properties control feature offers unprecedented control over your performance testing.You can update properties from your JMeter script while your test is running. 
Note that this feature replaces 'Adaptive Load Scenario' feature.

Changing Throughput in Real Time


We want to determine the capacity of our website in hits/s using JMeter's Constant Throughput Timer... the only problem is we only have a vague idea of what throughput to test at. 500 hits/s? 1000 hits/s? We are not sure. Using real time test control, we can make an initial guess about what the throughput should be, then update it as we see the results of the test.

To do so, we create our JMeter test script as normal, but in our throughput field, we put ${__P(hits)} . A property of this form signals to JMeter that it can be controlled during the test.



Now, we upload our script as normal, but when before we save our test configuration, we go to the Advanced Properties section, so that our throughput controller has an initial value.



Now, we give the property the same name as we did in the script, and select an initial value:



Okay, we have started our test, and with BlazeMeter's real time reporting, we find that our servers are doing fine with 500 hits/s. We can go to to the test page and reset the property like so.



Push Properties will update the value of the property. Pull Properties will displays the current value of the properties. View All will dump a variety of information from the server, including all of the test properties created in the manner I just described.

We play around with the throughput controller, and find that the max our server can handle is around 600 hits/s, then we hit view all.



Okay... so most of these are properties I don't need to worry about. Still good to have them available!

Helpful Hints


Note that when you are setting a throughput controller, the values are per server. For example, if your throughput controller is set to 250 hits/s, and BlazeMeter allocates your test 5 servers, your server will receive a throughput of 1250 hits/s from BlazeMeter.

The typical use case we envision for this feature is for users who need a load test that follows a step-function like pattern, i.e. "Okay, our servers can handle 1000 hits/s, let's try 1500 hit/s." It may also be used to turn load on-and-off over the duration of the test.

We hope you enjoy producing more robust and complex than ever before with this new feature.


BlazeMeter

provides a performance testing solution that's 100% compatible with Apache JMeter™

BlazeMeter Tutorials

  1. 200 MPH in neutral - Cloud-testing compared to traditional testing within the corporate LAN
  2. Analyze the Results of a Load Test Using BlazeMeter
  3. Real Time JMeter Properties Control with BlazeMeter
  4. BlazeMeter Formatters: Throughput
  5. Read Only Access to your Test Dashboard in Real-time
  6. Test X-Large Capacity Facebook Applications
  7. Dynamic Master/Slave Tests
  8. Load Test WordPress Sites
  9. Excluding Certain Domains from the Load Test
  10. Adaptive Load Scenario - How to Identify Performance Limits
  11. Folder Subscription
  12. Customize JTL Properties
  13. Download files from the Files tab
  14. How BlazeMeter simplifies maintaining JMeter scripts
  15. How can I download my site report?
  16. How can I make my report more detailed and present also embedded resources statistics
  17. How do I balance the "number of simulated users" on a test server?
  18. Using MSSQL JDBC Driver
  19. How to override basic JMeter properties from the test dashboard?
  20. How to setup a different CSV file for each JMeter engine?
  21. How to simulate .htaccess login
  22. Ignore Requests in the Reports
  23. IP spoofing / Hosts file modification
  24. JTL files and Real Time Reports
  25. Leveraging Cloud Computing for Load Testing of Web Applications
  26. Monitoring the JMeterEngine(s) Vital Signs
  27. Post Test Actions
  28. Presenting JTL files in BlazeMeter
  29. Recording HTTP traffic in the Cloud
  30. Running a SOAK test
  31. Select the Number of JMeter Engines
  32. Set JMeter Engine Command Line Arguments
  33. Set Load Geographical Origin
  34. Set the Console Command Line Arguments
  35. Set the JMeter Version
  36. Simulating logged in session using BlazeMeter
  37. [Master/Slave] Synchronize and Aggregate the Results from Several Test Sessions into a Single Aggregated Test
  38. Testing Amazon ELBs
  39. The Load Reports
  40. Upload Files
  41. Upload Proprietary JAR file
  42. Upload user.properties, system.properties and jmeter.properties Files
  43. Upload your JMeter Script
  44. Use Dedicated IP Addresses
  45. BlazeMeter Delayed Load Start
  46. Using Concurrent Pool Size - JMeter 2.5+
  47. Using CSV files with BlazeMeter
  48. Using Include Controller
  49. Using non-standard port. Unable to verify my site. Any workaround?
  50. Using Oracle JDBC Driver
  51. Using the Auto Scripting Feature with BlazeMeter
  52. Viewing Reports in GUI Mode
  53. SSL Manager and JKS files
  54. Using MySQL JDBC Driver
  55. Set the Time Zone
  56. How to Upload Many Files at Once
  57. Load Testing with HTTP Basic Authentication
  58. Input field and form submission
  59. Tests can end prematurely using JMeter 2.9
  60. Common File Storage
  61. Using BlazeMeter's Jenkins Plugin Behind a Corporate Proxy

Feedback and Knowledge Base