<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Certainly I can populate 100 queues with 1,000 messages each in a rather small fraction of a second with the PerfTest tool (<a href="http://www.rabbitmq.com/java-tools.html" target="_blank">http://www.rabbitmq.com/java-tools.html</a>) if the same message goes to all queues 1,000 times, or in less than 10 seconds if each message is distinct</blockquote>
<div><br></div><div>Quick question about using this perftest tool. I'm trying to use it to populate my test queues quicker for future tests, but I can't seem to get it to leave the messages in the queues. With a queue called "test", it was enough with amqp-publish to set the routing key to "test", and messages would get delivered to that queue. However, with this tool, I can see messages being delivered to the cluster, but they never make it to the queue or are retained there:<br>
<br>./runjava.sh com.rabbitmq.examples.PerfTest -k "test" -C 100000 -x 1 -y 0 -s 4 -f persistent<br><br></div><div>(I'm assuming the -s size is in bytes)<br><br></div><div>You're right that it does seem much faster, but without it actually storing to a queue it's hard to say whether it's even attempting the same operations. It appears as if this tool uses the "direct" exchange, which doesn't route anywhere, and so messages are immediately dropped. I can't seem to figure out how to use the default exchange, unlike amqp-publish, specifying the empty string as an exchange just causes a big java stack dump with this tool. Any suggestions?<br>
<br>Graeme<br><br></div></div></div></div>