Closed Chandhiramouli closed 1 year ago
Hi @Chandhiramouli That is really peculiar. I would expect a few milliseconds difference but I can't see where such a huge deviation would come from.
The only thing that happens between the sample measurements is the sending of the message. https://github.com/tilln/jmeter-iso8583/blob/1.2/src/main/java/nz/co/breakpoint/jmeter/iso8583/ISO8583Sampler.java#L154-L163
So, what may explain this is that your JVM is CPU constraint and doing other things (namely garbage collection) that may cause these additional delays.
How many threads are you running and what sort of hardware are you running on, with what JVM Heap parameters? Can you confirm that there is sufficient capacity to run your script?
We are performing the transaction with duration configuration, 8 Transaction per second with 10 minutes duration.
Processor - Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz 2.60 GHz (2 processors) Installed RAM - 12 GB Available RAM - 6.5 GB
JVM Heap size HEAP=-Xms1g -Xmx4g -XX:MaxMetaspaceSize=512m
8 Transaction per second with 10 minutes duration.
How does that relate to the 167314 samples displayed in the screenshot above?
Can you confirm that there is sufficient capacity to run your script?
Can you confirm this?
Also, how many actual timeouts are you experiencing?
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Error Description: We are defining the timeout in ISO8583 sampler response timeout, but we are receiving greater than the mentioned time in Aggregate table.
We are initiating the transaction with 5 second response timeout but request is active and giving the timeout in more than the defined time.
Steps to reproduce the behavior: 1)SET a response timeout in millisecond. 2)Run an Execution for 10min 3)Analyze the Aggregate Report Maximum Column.
Excepted behavior: We are setting response time in ISO8583 Sampler Timeout as 5000 milliseconds, the transaction should timeout within the given 5 seconds, but it is taking more than the configured timeout.
Reference screenshots: