<div>
<br>
</div>
<div></div>
<p style="color: #A0A0A8;">On Friday, March 8, 2013 at 8:40 AM, Simon MacMullen wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><blockquote type="cite"><div><div>Now for the warnings: 1) TURN OFF HIPE. This was testing with</div><div>Erlang R15B03 - the latest release and RabbitMQ 3.0.2. With HIPE and</div><div>the load we were putting on the system, Rabbit crashes bad, no</div><div>errors, no warning, it's just suddenly dead. It seems to happen a</div><div>few minutes into the load. I've not enabled any kind of debugging to</div><div>trace this down, but this was scary enough that we immediately turned</div><div>off HIPE everywhere.</div></div></blockquote><div><br></div><div>That certainly is scary, and unlike our experiences - we've generally </div><div>seen HiPE crash immediately or work fine. I suspect the platform is an </div><div>issue here. But yes, you should be cautious turning on HiPE in production...</div></div></div></span></blockquote><div>This is my experience as well on both CentOS 5.3 and 6.3 with R15B0 (and previous versions) with all versions of RabbitMQ we run (Everything from 2.7.1 -> 3.0.2)</div><div><br>
</div><div>Cheers,</div><div><br></div><div>Gavin</div>