My goal is to get a more accurate measure of the bandwidth of Bytes Over Time.
The general meaning of the load test:
- Download files using the HTTP GET request from the local host, save the contents of the files as different variables, such as ContentVar.
- Run the PUT loop. Put $ {ContentVar} in the body of the PUT requests.
When I analyze the resulting jtl file, I can see the correct "bytes" at the very beginning when I upload the files. (that is, a 1MB file that I upload, at this step, 1 MB of bytes will be displayed). However, all hosting requests show 493-494 bytes, even if they contain the contents of the files in their request bodies.
I would think that these PUTs should represent the size of the file that I load into the PUT + request a bit more for the header, etc.
What's happening? Not sure if this is relevant, but the tree listener does not display the contents of the PUT body. I'll see:
PUT data:
<actual file content, not shown here>
In version 2.x, I was able to see the contents of a raw HTTP request. Changing the view view.results.tree.max_size does not seem to help. Not sure if this is due to the low byte count.
I am using jmeter v3
source
share