>From jmeter site, it might be helpful to you!!
Listeners in the test plan send their results back to the client JMeter which writes the results to the specified files By default, samples are sent back as they are generated. This can place a large load on the network and the JMeter client. There are some JMeter properties that can be set to alter this behaviour. • mode - sample sending mode - default is Standard o Standard - send samples as soon as they are generated o Hold - hold samples in an array until the end of a run. This may use a lot of memory on the server. o Batch - send saved samples when either the count or time exceeds a threshold o Statistical - send a summary sample when either the count or time exceeds a threshold. The samples are summarised by thread group name and sample label. The following fields are accumulated: elapsed time latency bytes sample count error count Other fields that vary between samples are lost. o Stripped - remove responseData from succesful samples o StrippedBatch - remove responseData from succesful samples, and send as batches o Custom implementation : set the mode parameter to your custom sample sender class name. This must implement the interface SampleSender and have a constructor which takes a single parameter of type RemoteSampleListener. The following properties apply to the Batch and Statistical modes: • num_sample_threshold - number of samples in a batch (default 100) • time_threshold - number of milliseconds to wait (default 60 seconds) -- View this message in context: http://jmeter.512774.n5.nabble.com/JMeter-GUI-vs-JMeter-Server-tp4822852p4826216.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
