Currently DataStrippingSampleSender works this way: - If Sample is successful, it strips SampleResult response and children responses But if it is in failure, no stripping occurs. It was initially done to allow reporting errors to controller for better debugging. The problem with this is scalability when a lot of errors occur which can lead to OOM on Controller and slowdown jmeter-server. I suggest the following: - Add property sample_sender_strip_also_on_error which will default to true for performances - When true, we strip whatever the status, if not we only strip successful responses This will provide better scalability for next versions in case of high error rate and will still provide to users a way to debug distributed tests if they want at a lower rate.
Author: pmouawad Date: Thu Sep 15 11:52:24 2016 New Revision: 1760920 URL: http://svn.apache.org/viewvc?rev=1760920&view=rev Log: Bug 60137 - In Distributed testing when using StrippedXXXX modes strip response also on error Bugzilla Id: 60137 Modified: jmeter/trunk/bin/jmeter.properties jmeter/trunk/src/core/org/apache/jmeter/samplers/DataStrippingSampleSender.java jmeter/trunk/xdocs/changes.xml
Author: pmouawad Date: Sun Sep 25 16:16:04 2016 New Revision: 1762219 URL: http://svn.apache.org/viewvc?rev=1762219&view=rev Log: Bug 60137 - In Distributed testing when using StrippedXXXX modes strip response also on error Document sample_sender_strip_also_on_error Bugzilla Id: 60137 Modified: jmeter/trunk/xdocs/usermanual/properties_reference.xml
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4114