<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Thanks heasley i will check on the polling advice, as for TAC unfortunately my company doesnt have the budget for that.</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757">Enviado desde mi smartphone Samsung Galaxy.</div></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Mensaje original --------</div><div>De: heasley <heas@shrubbery.net> </div><div>Fecha: 29/03/2016 10:41 AM (GMT-03:00) </div><div>Para: nachofw <nachofw@adinet.com.uy> </div><div>Cc: heasley <heas@shrubbery.net>, rancid-discuss@shrubbery.net </div><div>Asunto: Re: High cpu on large configs </div><div><br></div></div>Tue, Mar 29, 2016 at 10:23:56AM -0300, nachofw:<br>> It is very inconvinient for my scenario, high cpu causes alerts on the monitoring systems creating false positive alerts. Also on other platforms causes packet loss por example cisco 3k series with large configs<br><br>the scheduler should not allow it to cause packet loss. you should open a<br>TAC case.<br><br>as for monitoring; i would alert on high cpu over a 5 minute or longer<br>interval, not a single poll.<br></body></html>