> Thanks, Jimmy. I have been looking into this issue a little more. I > couldn't exactly duplicate your numbers as my test machine did not have > sufficient memory but I believe I have identified the key symptom (JIRA > updated accordingly), though as yet not the root cause. > > As noted in the JIRA, it may be possible to tune your receivers to > mitigate the issue. How feasible that is probably depends on how closely > your real system follows the test scenario in the JIRA. For large > messages, reducing the capacity seems to be the most effective > improvement. As message size decreases, acknowledging in larger batches > becomes more effective.
I tried lowering the capacity in the albeit extreme testcase, and the issue was only resolved when I put it down to 1, which I can't do on my live systems as the performance will be too poor. However as noted below I've rerouted most of my large messages, which is okay for the time being. > One other question was just to confirm that the case as reported does > match your real system. Initially there was a suspicion that the ingest > process was blocked on send which would I think would be a different issue. I'm pretty sure this is causing at least some of my problems, as I've rerouted the main culprit of the large messages to a second broker, and now the main broker is much happier. The second broker exhibits the performance problems above, despite not having very many messages to process. However I think I'm still see some sends taking >30s on the main broker, however a lot less frequently than before, and not causing ring queue overflows. Possibly a separate issue, although could well be caused by the poor IO performance of the VM its running on which should hopefully be resolved soon, so I will test further then. > I'll do some more digging on what the root cause from the drop in > throughput for large messages on a full ring queue might be and update > the JIRA with any progress. Thanks! Jimmy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
