Out of the box, JMeter provides a way to perform distributed testing. This comes in the form of a master-slave setup. In this mode, there is a machine known as a master, which controls a number of client machines (JMeter instances) known as slaves. This approach has some benefits, including managing multiple JMeter instances remotely from the master node, automatically collecting test results from all slave nodes and aggregating them into a single report, and replicating test plans from the master node to slave nodes without the need to copy them to each server. That said, it also has some drawbacks, with the major one being the master quickly becoming a bottleneck as a result of collecting information from slaves in real time. In our experience, we have found this approach doesn't scale well if you have more than a couple of slave nodes. Refer to the other recipes in this chapter to see how to get past this hurdle.
JMeter Cookbook
By :
JMeter Cookbook
By:
Overview of this book
Table of Contents (16 chapters)
JMeter Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
JMeter Fundamentals
Handling Responses
Building Robust Test Plans with Controllers
Testing Services
Diving into Distributed Testing
Extending JMeter
Building, Debugging, and Analyzing the Results of Test Plans
Beyond the Basics
Installing the Supporting Software Needed for this Book
Index
Customer Reviews