I would imagine JMeter returns the size of the http response, not the size of the uploaded data. What does the Content-Length header return for your request? I would imagine it's a constant number, regardless of how many bytes you PUT
Example with wget, it's similar with curl wget -S -O /dev/null --method=PUT --body-data="123456789012345678901234567890123456789012345678901234567890" http://... best regards Ivan On Fri, Sep 30, 2016 at 7:52 PM, Ahmad A <[email protected]> wrote: > HiI am using HTTP PUT with HTTPClient4 implementation with different file > sizes and then GET to retrieve them back.The JTL file is being populated > correctly and showing the expected latency for both PUT and GET. > On the other had, bytes capture in JTL is incorrect for PUT (But they are > correct for GET). Consequently this is causing the kb/s calculations to be > incorrect since the bytes are incorrect for PUTs. > Is that a configuration issue that I need to change on my side or is this > a bug??? > > > Formatted sample of JTL output (see the contrast between the PUT and GET > in bytes)timeStamp,elapsed,label,responseCode,responseMessage, > threadName,dataType,success,failureMessage,bytes, > grpThreads,allThreads,Latency,IdleTime2016/09/23 22:51:44.106,621,039_ > PUT20MBObj,201,Created,PUT20MBObj_ThrdGrp > 39-5,text,true,,464,6,6,xyz,02016/09/23 > 22:52:22.121,3511,040_PUT100MBObj,201,Created,PUT100MBObj_ThrdGrp > 40-7,text,true,,464,1,1,xyz,02016/09/23 22:58:24.541,773,053_ > GET20MBObj,200,OK,GET20MBObj_ThrdGrp > 49-10,text,true,,20972023,1,1,xyz,02016/09/23 > 22:58:57.551,2697,054_GET100MBObj,200,OK,GET100MBObj_ThrdGrp > 50-6,text,true,,104858104,1,1,xyz,0 > > > Thank you.. > > Ahmad
