> On Feb 6, 2020, at 8:03 PM, Andrew Burton <[email protected]> wrote: > > Hi Dale, > > I believe if you enable "Save response as MD5 hash" it will not store the > result, which is likely where JMeter runs into issues with large files (see > the comments for this setting in > https://jmeter.apache.org/usermanual/component_reference.html#HTTP_Request)
Ah, ok. I have to admit I considered this option but reasoned that, to be able to hash the response, it needs to save it in its entirety either in memory on on disk... which is what I was trying to avoid in the first place. It wasn't entirely clear from the documentation that one would be spared from memory issues. Thanks for pointing that out, it does seem to do the trick. > Out of curiosity, how often are you going to be dishing up these 1Gb files > in Prod? You might run into issues simulating this, and instead end up > saturating the network for your load generators. Returning a 1Gb payload > for an API request sounds like it could open up some real issues (if I'm > interpreting your use case correctly). Fair question. We have a range of network types available in our test environment, including 10, 40, and 100Gb ethernet to the servers. The 1GB files aren't being served as part of the actual API itself, but as a part of a larger scenario that involves many devices querying an API for the availability of any software upgrades and then reacting appropriately to what the API informs them. /dale --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
