On 5 February 2013 15:39, Sergio Boso <[email protected]> wrote: > I recently went through a situation where I had to download some 300MB+ > files. > > In fact, it seems that Jmeter tries to keep the sample result in memory > until the operation has finished. > I assume that this is done in order to do allow assertion, content analysis
Yes. > etc, but where very large files are involved, this is a real issue. Which is why there is the HTTP option "Save response as MD5 hash?" > I made a quick workaround using OS sampler + wget command+ delete file > command. > I think that an option to save the sample result to file, would be more > appropriate. Feel free to raise an enhancement issue - even better, include a patch. > HTH > Sergio > > > Il 05/02/2013 02:27, Stott, Charlie ha scritto: > >> First solve your out of memory issues, then you may be able to load a >> large file into memory. >> >> Most common cause of memory issues in gui are listeners, particularly >> results tree. Try only recording errors if you need it at all. Gui is >> intended for testing your tests, rather than doing your load testing. >> >> AFAIK, in non-gui tests it is likely older HTTP implementations, use v4+. >> I never get memory issues in CLI tests. >> >> However, 100MB filetostring does not really sound like something I'd want >> to do, are you sure it is the best design? >> >> Charlie >> > > > -- > > Ing. Sergio Boso > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
