Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Support variable for all JMS messages (bytes, object, ...) and sources (file, folder) #241
Source code is based on Java 8 and unit tests has been added. Message format processing has been moved to a dedicated package, same for cache support.
An encoding field has been added to UI. It is by default filled with two special values (
Cache system use a single field in PublisherSampler, so explicit type of cached content is not known. It may be improved (replaced ?) by using Guava instead. Cached content isn't consistent for a message type (bytes, object, ...) but also depends if raw mode is used or not. For all non-raw mode, text is always cached to permit variable processing for each sampler execution.
Two new components were added to JMeter test API:
Special notes: in order to check encoding management, test resources encoding must be preserved. By default, all files are in UTF-8 ; except for: cp1252.txt, object_cp1252.txt, object_prolog_cp1252.xml,
Yes, it finally replaces #239. I have first supposed both will be merged, but finally rewritten to improve clean code with separation of concerns.
Regarding performance, "raw" mode may have few overhead. Variable support should act exactly as if text area was used. I will try to make some check with microbenchmarking.
Send 200000 messages share on 2 threads to a JMS topics (text format on a local ActiveMQ broker )
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.
I use this patch in production for 3 month with big load and big data without any problem of performance.
Sorry if I did it to quickly....