Date: 2004-10-06T06:25:26 Editor: PeterLin <[EMAIL PROTECTED]> Wiki: Apache JMeter Wiki Page: JMS Sampler URL: http://wiki.apache.org/jakarta-jmeter/JMS Sampler
no comment Change Log: ------------------------------------------------------------------------------ @@ -13,6 +13,9 @@ * ConnectionFactory - server specific setting * Topic - the specific topic for the test * Iterations - number of iterations to aggregate + * use 1 connection for N producers/consumers (suggested by james) + * use N/2 connections for N producers/consumers (suggested by james) + * use N connections for N producers/consumers (suggested by james) * Message type - TextMessage, ObjectMessage * random message - similar to how webservice sampler can randomly select a message * Text area - for message @@ -20,4 +23,4 @@ The sample Aggregator is needed to aggregate several samples together, since a single publish will probably less than 1 millisecond, it's a good idea to run X iterations and record the time. -By having a publish and subscribe sampler, it means a single test plan can have two thread groups running concurrently. One thread group can have X threads publishing, while the thread group for the subscribers can have a different number of threads. this should allow for a wide variety of test scenarios. +By having a publish and subscribe sampler, it means a single test plan can have two thread groups running concurrently. One thread group can have X threads publishing, while the thread group for the subscribers can have a different number of threads. this should allow for a wide variety of test scenarios. Using the same connection for N producers/consumers will measure the effect of connection on performance. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
