Measured transaction throughput and response times are critical data of any ArcGIS Enterprise load test, but captured hardware utilization of the deployment machines provide vital information as well. Together, these test artifacts allow for the proper analysis of the capabilities and efficiencies of the Site.
Determining that an application or feature service has achieved a particular level of throughput is good, but confirming the scalability characteristics while also examining the captured processor utilization of the tested workload is even better.
This Article will discuss several ways to capture the machine hardware utilization. This resource usage is a great compliment to the results of an Apache JMeter load test of ArcGIS Enterprise and can help further the analysis. The Article will focus on the most common scenarios using free tools and utilities for Windows and Linux.
Table Of Contents
- Capturing Hardware Utilization During an Apache JMeter Load Test
- Capturing Strategies
- What Information Should the Load Test Capture?
- Sample Interval
- The Difference Between Capturing and Monitoring
- Test Clients (Load Generator Machines)
- Understand Your Server Baselines
- Common Utilization Capturing Examples
- Using Perfmon (To Capture Utilization Outside of Load Test)
- Using dstat (To Capture Utilization Outside of Load Test)
- Using Apache JMeter (To Capture Utilization Directly From Load Test)
- The SampleWorldCities Test Plan With Metric Collection Support
- Components of the Test Plan
- jp@gc - PerfMon Metrics Collector Extension
- Validate the JMeter-to-ServerAgent Connectivity
- Test Execution
- General Methodology Guide
- Common Utilization Collection Challenges
- Final Thoughts