Github user max3163 commented on the issue:
https://github.com/apache/jmeter/pull/241
Protocol :
Send 200000 messages share on 2 threads to a JMS topics (text format on a
local ActiveMQ broker )
Send 200000 messages share on 2 threads to a JMS topics (binary format on a
local ActiveMQ broker )
1. JMeter 3.1 :
- Throughput :
BINARY : 11 400 tps
TEXT : 11 600 tps
2. JMeter 3.2 with PR #241
- Encodage ROW
Throughput :
BINARY : 12 700 tps
TEXT : 11 500 tps
- Encodage UTF-8 ( no variable in JMETER )
Throughput :
BINARY : 11 700 tps
TEXT : 9 650 tps
- Encodage UTF-8 ( with variable set in JMeter )
Throughput :
BINARY : 12 000 tps
TEXT : 9 700 tps
As you can see, other than one impact on the binary side when you activate
the Encodage â and itâs normal as the file is interpreted - the results are
almost identical.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
