<div dir="ltr"><div>Hello again,</div><div> </div><div> I built a new recommended rabbit mq cluster with version 3.2.1 (Erlang R16B) to avoid the the memory leak issue that I mentioned in the mail below. After building this cluster, I migrated 50% traffic on highest volume queue (this queue constitutes to 70% of the total our traffic).</div>
<div><br></div><div>Cluster Version v3.0.2 v3.2.1</div><div>Erlang R13B R16B</div><div># nodes 2 2 </div>
<div># Connections 850 250</div>
<div>Erlang process 2900 1500</div><div>Publish/Delivery rate 230 / sec 160 / sec</div><div><b>Cpu Usage 15% 25%</b></div>
<div><b># Running process 2 3-4</b></div><div><br></div><div><br></div><div>After the migration, I am noticing higher cpu usage and total number of running processes on new cluster for less traffic than the original cluster. Also, when is there is an increase in traffic on both clusters, cpu on new cluster increases significantly than increase in old cluster. For instance, an increase in 0.4 MB network traffic over 2 mins caused an increase in cpu of 2% in old cluster vs 6% increase in new cluster. </div>
<div><br></div><div>So I would like to understand why I am noticing increase in cpu and total number of running processes before migration the whole traffic to new cluster. Is this expected with new cluster? I tried searching but couldn't find any posts/blogs explaining this scenario. </div>
<div><br></div><div>Pls let me know if you need more info on cluster configs.</div><div><br></div><div>Thanks,</div><div>Shri</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 2, 2014 at 6:44 AM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi,<br>
<div><br>
On 27/12/13 16:55, shridharan muthu wrote:<br>
<br>
> I know the quick answer is "upgrade" but is there a short term solution<br>
> to fix this before we upgrade?<br>
<br>
<br>
</div>Please check whether you can reproduce the problem on the latest version<br>
of the broker. There have been numerous improvements to the broker since<br>
3.0.2. If you can reproduce the problem then please supply the output of<br>
"rabbitmqctl report" while the memory usage is normal and again when it<br>
is abnormal.<br>
<span><font color="#888888"><br>
<br>
<br>
<br>
-Emile<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div></div>