RabbitMQ Performance Testing Tool Introduction:
Https://www.rabbitmq.com/java-tools.html
RabbitMQ Performance Testing Tool Download:
Https://github.com/rabbitmq/rabbitmq-perf-test/releases
Unzip the file (put it in the RabbitMQ installation directory)
Rabbitmq-perf-test-1.1.0.zip
Test (command line execution):
> CD D:\Program files\rabbitmq server\rabbitmq-perf-test-1.1.0\bin> runjava.bat com.rabbitmq.perf.perftest-a
More help:
> Runjava com.rabbitmq.perf.PerfTest--helpusage:<Program>-?,--help show Usage-a,--multiackevery<Arg> Multi ack every-a,--autoack auto Ack-b,--Heartbeat<Arg> Heartbeat interval-c,--pmessages<Arg> Producer Message count-c,--confirm<Arg> Max unconfirmed publishes-d,--cmessages<Arg> Consumer message count-d,--ID<Arg> Test id-e,--Exchange<Arg> Exchange NAME-F,--flag<Arg> Message flag-h,--URI<Arg> Connection Uri-i,--interval<Arg> Sampling interval in seconds-k,--randomroutingkey use random routing key per message-k,--Routingkey<Arg> Routing key-m,--Framemax<Arg> Frame max-m,--ptxsize<Arg> Producer TX size-n,--ctxsize<Arg> Consumer TX size-p,--predeclared allow use of predeclared objects-q,--Globalqos<Arg> Channel prefetch count-q,--QoS<Arg> Consumer prefetch count-r,--consumerrate<Arg> Consumer rate limit-r,--rate<Arg> Producer Rate limit-s,--size<Arg> Message size in bytes-t,--type<Arg> Exchange Type-u,--queue<Arg> Queue Name-x,--producerchannelcount<Arg> channels per producer-x,--producers < arg> producer Count-y,--consumerchannelcount <arg> channels per consumer-y,--consumers < arg> consumer count-z,--time <arg > run duration in seconds (unlimited by default)
Example: 100 producers; 100 consumers; the Echange name is called Testex; the forwarding type is fanout;queue called testque;bingding for kk01;
Runjava.bat com.rabbitmq.perf.perftest-x100-y100-e "Testex"-T "fanout"-U "testque"-K "Kk01"
Using Perftest
The most basic way to run Perftest is to specify the URI to be connected, the Publisher to use (say 1), and some consumers (such as 2). Note that the RabbitMQ Java client can achieve a high release rate (up to 80 to 90K messages per second for each connection), give enough bandwidth, and when certain security measures (publisher acknowledgement) are disabled, it is seldom necessary to over-configure the publisher (unless this is a specific test target).
Bin/runjava com.rabbitmq.perf.perftest-x 1-y 2-u "Throughput-test-1"-A--id "Test 1"
Use 2 publishers and 4 consumers:
Bin/runjava com.rabbitmq.perf.perftest-x 2-y 4-u "Throughput-test-2"-A--id "Test 2"
This modification switches the consumer to a manual acknowledgment:
Bin/runjava com.rabbitmq.perf.perftest-x 1-y 2-u "throughput-test-3"--id "Test 3"
Modify change message size from default (12 bytes) to 4 KB:
Bin/runjava com.rabbitmq.perf.perftest-x 1-y 2-u "throughput-test-4"--id "Test 4"-S 4000
Using durable queues and persistent messages:
Bin/runjava com.rabbitmq.perf.perftest-x 1-y 2-u "throughput-test-5"--id "test-5"-F Persistent
---------------------This article from Xin Xiuzan csdn Blog, full-text address please click: 78827135?utm_source=copy
View and learn about messaging with the Rabbitmq-management interface tool (refer to: RABBITMQ installed in Windows)---------------------This article comes from the CSDN blog of Huang-zc, Full Text address please click: 55252797?utm_source=copy
RabbitMQ Performance Testing Tool performance testing tools