DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

How does AI transform chaos engineering from an experiment into a critical capability? Learn how to effectively operationalize the chaos.

Data quality isn't just a technical issue: It impacts an organization's compliance, operational efficiency, and customer satisfaction.

Are you a front-end or full-stack developer frustrated by front-end distractions? Learn to move forward with tooling and clear boundaries.

Developer Experience: Demand to support engineering teams has risen, and there is a shift from traditional DevOps to workflow improvements.

Related

  • Tips for Efficiently Testing and Validating Your Program
  • Implementing DDoS With MuleSoft: Demonstration With Apache JMeter
  • Client-Side Performance Testing
  • Exploring Cloud-Based Testing With the Elastic Execution Grid

Trending

  • Apache Doris and DeepSeek: Redefining Intelligent Data Analytics
  • Smarter IoT Systems With Edge Computing and AI
  • From OCR Bottlenecks to Structured Understanding
  • Beyond Java Streams: Exploring Alternative Functional Programming Approaches in Java
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Testing, Tools, and Frameworks
  4. JMeter — How to Distribute User Load in the Test Plan

JMeter — How to Distribute User Load in the Test Plan

Learn how to distribute load in a website performance test plan with JMeter.

By 
Rupesh Garg user avatar
Rupesh Garg
·
Nov. 05, 18 · Tutorial
Likes (8)
Comment
Save
Tweet
Share
14.8K Views

Join the DZone community and get the full member experience.

Join For Free

You might have encountered this situation where not all users would do a particular scenario all the time. Let's consider an e-commerce application, having the major scenarios user login, search, browsing the application by an anonymous user, product added to cart, and buying the product. For example:

  • 40% authenticated users logging into the website
  • 30% of anonymous users browsing the website
  • 20% of users doing a search
  • 9% of users adding a product to the cart
  • And 1% of all users actually buying the product

To mimic this behavior in a load test script, we use the Throughput Controller which controls how often a particular scenario should be executed. The controller contains two modes:

  • Percent Executions
  • Total Executions

Now we will see how these two modes can be executed in the test plan:

Consider 100 users/threads to be run. Percent Executions mode commands the controller to execute a certain percentage of the iterations through the test plan as defined in the Throughput textbox shown below:Image title

As you can see below, after execution of the Test Plan, the samplers have executed according to the frequency (throughput) set in each request.

Image title

Total Executions mode commands the controller to stop executing after a certain number of iterations have completed as given by the Throughput textbox shown below.

Image title

As you can see below, the samplers have executed as per the limit defined in Total Executions, instead of all requests hitting with 100 users.

Image title

If the Per User checkbox is checked, the controller executes per user/thread basis. If unchecked, then the calculation will be global for all users.

Let's understand the Per User case with an example. Say our test configuration is 100 users and the duration of the test plan is 300 seconds.

Image title

Let's use total execution mode and check Per User.

Image title

As you can see, the total number of executions is equal to the number of users times the number given for throughput.

Image title


Test plan Testing

Opinions expressed by DZone contributors are their own.

Related

  • Tips for Efficiently Testing and Validating Your Program
  • Implementing DDoS With MuleSoft: Demonstration With Apache JMeter
  • Client-Side Performance Testing
  • Exploring Cloud-Based Testing With the Elastic Execution Grid

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • [email protected]

Let's be friends: