Add new thread variable __jmv_THREAD_START_TIME_ITERATION contains the currentTimeMillis when the thread iteration start. #6356
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
September 26, 2024 15:26
…e currentTimeMillis when the thread iteration start. Corresponding to the issue (new feature): apache#6319
…ntTimeMillis when the thread iteration start in the section "6 Pre-defined Variables"
FSchumacher
reviewed
Sep 27, 2024
| @@ -1765,6 +1765,8 @@ However some variables are defined internally by JMeter. These are listed below. | |||
| <li><code>JMeterThread.last_sample_ok</code> - whether or not the last sample was OK - <code>true</code>/<code>false</code>. | |||
| Note: this is updated after PostProcessors and Assertions have been run. | |||
| </li> | |||
| <li><code>__jmv_SAME_USER</code> - is the same user for each iteration ? <code>true</code>/<code>false</code>. Mainly impacts clean cookie, cache data and new connection</li> | |||
There was a problem hiding this comment.
Is this to fix some older code?
There was a problem hiding this comment.
Is this to fix some older code?
Yes, when i search this variable "__jmv_SAME_USER" in the documentation, i don't see it.
So i add this line about the variable __jmv_SAME_USER.
And i add the new one variable "__jmv_THREAD_START_TIME_ITERATION"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Corresponding to the issue (new feature): #6319
Description
Add a new unmodifiable JMeter Thread variable named "__jmv_THREAD_START_TIME_ITERATION"
Motivation and Context
It is interesting to know the start timestamp of a thread iteration to calculate cadences or pacing.
This variable can also be used to help other Thread Groups calculate cadences (E.g : Concurrency Thread Group or may be Open Model Thread Group)
How Has This Been Tested?
Yes, add a groovy sampler first sampler of the thread group and compute the delta between the value in the variable __jmv_THREAD_START_TIME_ITERATION and the current time System.currentTimeMillis() in the groovy sampler.
Groovy code
+++++++++++++++++++++++++++
long currentTime = System.currentTimeMillis();
long startThreadIter = Long.parseLong(vars.get("__jmv_THREAD_START_TIME_ITERATION"));
long delta = currentTime - startThreadIter;
return delta;
+++++++++++++++++++++++++++
Results 0 or 1 ms
Screenshots (if appropriate):
Types of changes
Checklist:
Add new variable __jmv_THREAD_START_TIME_ITERATION in the documentation :
functions.xml, section 6 Pre-defined Variables