Bug 61087 - Stripping Mode only strips response data not request data
Summary: Stripping Mode only strips response data not request data
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 3.0
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2017-05-12 03:59 UTC by Tim Terrill
Modified: 2017-07-22 14:01 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Tim Terrill 2017-05-12 03:59:55 UTC
Our organization occasionally runs fairly large-scale load tests involving 10+ load generation blades in multiple blade centers against large infrastructures.  During one particular large scale load test involving SAML flows, the bottleneck in the load testing suite was ultimately the network bandwidth to the blade centers housing the load generator "master" node that was receiving all the simple data writer (SDW) CSV data.  Upon investigation it was determined that even though we were using "Stripped Async" mode for the SDW, which strips off the RESPONSE data, it was still sending all the REQUEST data (including a somewhat large SAML document) back to the master. This required us to run multiple masters each with 3 slaves in order not to eat up a Gigabit ethernet link to the masters.  However, the blade centers 2 Gigabit uplinks then ultimately became saturated.

It is my belief that the SDW should only be sending the actual CSV data to the master.  If my understanding is wrong, perhaps I ought to look into creating my own custom "CSV Data Writer" or some such thing...

We are planning to capture some tcp dumps to verify this on the latest version of JMeter and will post more information when we get it.

Thank you,
Comment 1 The ASF infrastructure team 2022-09-24 20:38:08 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4389