<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 9, 2013 at 10:18 AM, Hopkins, Charles G. <span dir="ltr"><<a href="mailto:charlesghopkins@gmail.com" target="_blank">charlesghopkins@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I'm sure this has probably been asked before, but why was the number 20 chosen as the number of pings to use for SmokePing?<div>
<br></div>Sincerely,<br><div><div><div dir="ltr"><br><i style="font-family:comic sans ms,sans-serif;color:rgb(102,0,0)"><font size="4"><b>Chaz</b></font></i><br>
<br></div></div></div></div></blockquote></div><br></div><div class="gmail_extra">The more data you have, the more the smoke is more relevant. Since the smoke is essentially measuring jitter, or at least the variance between multiple ping response times, the more that are tested and recorded the more useful the data can be. Plus you can set the size of the pings to something smaller if it helps but really, if your network can't handle that many pings then there is something else to be concerned about. If pings are making the top of any utilization graph then I would guess that network path isn't very highly utilized at all and there really shouldn't be anything to worry about. Sure, oodles and oodles of pings can look daunting, especially to a nubile network admin who just got a hold of wireshark or netflow for the first time...<br>
</div></div>