Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Master Apache JMeter - From Load Testing to DevOps

You're reading from   Master Apache JMeter - From Load Testing to DevOps Master performance testing with JMeter

Arrow left icon
Product type Paperback
Published in Aug 2019
Publisher
ISBN-13 9781839217647
Length 468 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (3):
Arrow left icon
Bruno Demion (Milamber) Bruno Demion (Milamber)
Author Profile Icon Bruno Demion (Milamber)
Bruno Demion (Milamber)
Antonio Gomes Rodrigues Antonio Gomes Rodrigues
Author Profile Icon Antonio Gomes Rodrigues
Antonio Gomes Rodrigues
Philippe Mouawad Philippe Mouawad
Author Profile Icon Philippe Mouawad
Philippe Mouawad
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

About the Book 1. Quick Start with JMeter FREE CHAPTER 2. JMeter Overview 3. Designing a Test Case 4. Important Concepts in JMeter 5. Preparing the Test Environment (Injectors and Tested Systems) 6. Being Productive with JMeter 7. Load Testing a Website 8. Load Testing Web Services 9. Load Testing a Database Server 10. Load Testing Message-Oriented Middleware (MOM) via JMS 11. Performing a Load Test 12. Visualizing and Analyzing the Load Testing Results 13. Integration of JMeter in the DevOps Tool Chain

Parameters to Take into Account when Creating a Scenario

Our list of scenarios is defined, but there are still many challenges in order to implement them in the most realistic way.

Here is a non-exhaustive list of important parameters for the implementation of our scenarios.

Vary User Input

In order to avoid testing only the performance of the cache of the targeted solution, it is necessary to vary the user inputs (values in the forms, login/password, and so on).

On the other hand, do make sure that you don't overly diversify the user input values at the risk of ending up with an application cache that appears to be inefficient because of an unrealistically wide data range.

Note

Monitor the metric cache hit ratio delivered by cache servers to validate the fact that the inputs chosen reflect reality.

If the hit ratio is too high, and higher than the production cache hit ratio, the dataset is not large enough.

If the hit ratio is too low, and lower than the production cache hit ratio, the dataset...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime