jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 62045] timing difference for large (?) requests
Date Sun, 28 Jan 2018 18:43:20 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=62045

--- Comment #4 from Alex Podelko <apodelko@yahoo.com> ---
No, I didn't change that parameter:

# Max size of bytes stored in memory per SampleResult
# Ensure you don't exceed max capacity of a Java Array and remember 
# that the higher it is, the higher JMeter will consume heap
# Defaults to 0, which means no truncation
#httpsampler.max_bytes_to_store_per_request=0

Not sure what read buffer you are asking about - could you please elaborate?

There is some variability between runs, but it is very small comparing to the
difference between JMeter and Fiddler. And yes, it remains constant - I am
running tests tests with each build. All happens inside one data center, so
latency is <1ms.

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message