> For the complete documentation index, see [llms.txt](https://wiki.loadium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.loadium.com/jmeter-corner/jmeter-timers.md).

# JMeter Timers old

## Why Do I Need a Timer in JMeter?

User behavior in [load tests](https://loadium.com/blog/record-and-play-load-testing-in-5-steps/) depends on many factors. Those factors can be “ramp-up time”, “user count on the system in a specific time interval”, etc. and most of them rely on timing. **The time between user actions defines the realism of the scenario.** That’s why JMeter offers various Timer for you to use in your performance test projects.

By default, [JMeter](https://loadium.com/blog/websocket-with-apache-jmeter/) executes all samplers one after another. There is no delay between sampler’s execution. This makes our tests non-realistic because no user goes into a page and clicks to a link, then does another request. A user thinks, reads, writes in a web or mobile app. So all those times are the key characteristic of your scenario. In [performance testing](https://loadium.com/blog/performance-testing-with-postman/), this is called “**think time**”. Testing without a [JMeter](https://loadium.com/blog/handling-error-messages-of-jmeter-tests-in-loadium/) timer can create irregular test results because the simulated requests will come in a different pattern than what is seen in a real-world situation.

## Timer Types

In JMeter, there are 9 different Timer types.

1. Constant Timer
2. Uniform Random Timer
3. Precise Throughput Timer
4. Constant Throughput Timer
5. Gaussian Random Timer
6. JRS223 Timer
7. Poisson Random Timer
8. Synchronizing Timer
9. BeanShell Timer

Each timer has its own behavior. Let’s have a look at some major Timers.

**Constant Timer:**  This is the most basic timer [JMeter](https://loadium.com/blog/tag/jmeter/) provides. All Samplers will wait a constant time interval according to the value you provided. The thread delay is in milliseconds.

**Uniform Random Timer:**  This timer lets your Samplers wait in a specific time interval according to the given values. You should provide two values. First one is the constant delay, the second one is the random delay.

{% hint style="success" %}
***Example***

Constant Time: 500ms

Random Delay: 100ms

Our samplers will wait x amount of milliseconds between 400ms and 600ms.
{% endhint %}

**Gaussian Random Timer:** It follows a normal or Gaussian distribution method. It provides a delay based on a constant and standard deviation.

**JRS223 Timer and BeanShell Timers:** They both require you to write some scripts by using javascript, groovy or [BeanShell](https://loadium.com/blog/beanshell-processor-tutorial-1-basic-usage/) scripting language.

## How to Use Timers

We recommend you to use scoping articles that we recently published. [Scopes in JMeter](https://loadium.com/blog/scopes-in-jmeter/)

There are examples that you can look into.

Happy [load testing](https://loadium.com/blog/benefits-of-load-testing-on-the-cloud/)!

{% content-ref url="/pages/-MUQ5cTQeTV9Yioro2zC" %}
[Getting Started with Loadium](/getting-started.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MUSAunBwe2J09CIl1hu" %}
[JMeter Test](/create-test/jmeter-test.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MUT5hLDUtoTsSYDaFkV" %}
[Pricing OLD](/about-loadium/pricingold.md)
{% endcontent-ref %}

If you don't see the answer to your question here, please [reach out to us](https://loadium.com/contact-us/) to let us know! We're always improving our documentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.loadium.com/jmeter-corner/jmeter-timers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.