> If there are a lot of samples, this may just cause the servers to run > out of memory. > > Perhaps try Statistical.
Works great! ./jmeter -n -r -t my_test.jmx -l log.jtl ... except that the results returned is always 0 for latency on the distributed test. (i.e. using -r) and I get proper latency results for the same non-distributed test. Elapsed Time is always ok. I did a 'diff' on the jmeter.properties for all the machines and they are all the same. jmeter.properties: (only "timestamp", "latency" and "elapsed" is 'true') jmeter.save.saveservice.data_type=false jmeter.save.saveservice.label=false jmeter.save.saveservice.response_code=false # response_data is not currently supported for CSV output #jmeter.save.saveservice.response_data=false # Save ResponseData for failed samples #jmeter.save.saveservice.response_data.on_error=false jmeter.save.saveservice.response_message=false jmeter.save.saveservice.successful=false jmeter.save.saveservice.thread_name=false jmeter.save.saveservice.time=true jmeter.save.saveservice.subresults=false jmeter.save.saveservice.assertions=false jmeter.save.saveservice.latency=true #jmeter.save.saveservice.samplerData=false #jmeter.save.saveservice.responseHeaders=false #jmeter.save.saveservice.requestHeaders=false #jmeter.save.saveservice.encoding=false jmeter.save.saveservice.bytes=false #jmeter.save.saveservice.url=false #jmeter.save.saveservice.filename=false #jmeter.save.saveservice.thread_counts=false Sounds like a bug? Any suggestions? Thanks Christiaan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
