Hi all,
I'm poking the list here as a relatively novice jmeter user look for some advice, as my google-fu has failed me and I can't seem to find a straight-forward solution to the predicament that I've ran into. I hope I haven't missed something obvious, and kind pointers to the right place are appreciated if I have. I'm trying to simulate a full application-API conversation in order to load-rate the infrastructure that serves the API. One of the requests in the conversation involves fetching a ca. 1GB file and my only interest is to see how long it takes to download and other such basic connection statistics. I am not interested in its contents (it's just a static binary file), or anything of the sort. As soon as any bytes are received, the relevant counters should be updated and those bytes deallocated or nulled out into the oblivion, never to occupy memory again. The seasoned among you might already identify the problem I'm running into: jmeter quickly croaks while ingesting this large file with a OOM exception, as the default HTTP sampler appears to be trying its best to stuff the whole thing into memory as its bits come in off the wire. Understandable, given that I suppose it queues up the information for any post-processors to consume, but in this case there aren't any and never will be. I guess what I'm looking for is essentially a "null" HTTP sampler - where ingested bytes are immediately tossed after they're accounted for. No stuffing into byte arrays or filestreams or anything of the sort. I *hope* this would be a solution to my problem, and I acknowledge that the problem may be more nuanced than it appears to me. Anyone have some good ideas? TIA, /dale --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
