Hi Lorenz,
Thanks a lot for your response and explaining the flow to disk algorithm in
detail. I have described the test setup in detail in the first email of
this thread, to summarize the points again:
a) There is only one virtual host.
b) There are 6000 queues in this virtual host, but messages
+1
* checked all checksums
* started broker created queue via web management console
* ran Hello example
On 20/12/16 12:27, Keith W wrote:
Making my +1 explicit.
My testing was:
1) Verified the md5/sha checksums on all distribution artefacts
2) Verified signatures on all all distribution
+1
I performed the following testing of 6.0.6 broker and client:
* started the broker
* created and bound a test queue using Web Management Console
* created a sample maven project with client dependencies from staging
repo and send/recieve messages using 0.10 and 0.9 AMQP protocols
Hello Ramayan,
glad to hear that the patch is (mostly) working for you.
To address your points:
1. If indeed in one case flow to disk is kicking in while in
the other one it is not, then I am not surprised that
there is a 5% difference. The question is whether the
flow
