[smokeping-users] Is there a "blazemode" for TCPPing (Smokeping 2.004002)

[G.W. Haywood]

Hi there,

On Tue, 24 Nov 2009, Mark Dawson wrote:

> We want to ignore the first packet from our TCPPings so that we have more
> reliable measurements on our runs.  I see that this feature is offered for
> Fping in the newest version of Smokeping.
>
> Does something exist like this for TCPPing?

This is what I did to the FPing probe to deal with this issue.
I'm sure you can do the same to the TCPPing probe.

> The information in this e-mail is intended only for the person or entity to which it is addressed.
>
> It may contain confidential and /or privileged material...

Yeah, right.  Can't you get rid of this stuff for mailing lists?

--

73,
Ged.

---------- Forwarded message ----------
Date: Fri, 23 May 2008 15:25:32 +0100 (BST)
From: G.W. Haywood <ged at jubileegroup.co.uk>
To: Smokeping users' mailing list <smokeping-users at lists.oetiker.ch>
Subject: Less smoke.

Hi there,

It's very common for the RTT of the first ping in a series to be much
greater than those subsequent.  This is easily explained because there
may be much more work for the routers etc. along the way to do for the
first packet, they have to populate ARP caches for example.

However this can give very misleading statistics in some cases.  I've
modified my copy of FPing.pm to send one more ping than requested, and
then to discard the first returned RTT value.

8<----------------------------------------------------------------------
*** FPing.pm.original	2008-05-23 15:02:39.000000000 +0100
--- FPing.pm	2008-05-23 15:08:15.000000000 +0100
***************
*** 32,37 ****
--- 32,40 ----

  The (optional) B<packetsize> option lets you configure the packetsize for the pings sent.

+ This version of FPing sends one more ping than requested, and discards
+ the first RTT value returned as it's likely to be an outlier.
+
  The FPing manpage has the following to say on this topic:

  Number of bytes of ping data to send.  The minimum size (normally 12) allows
***************
*** 121,127 ****

      my @cmd = (
                      $self->binary,
!                     '-C', $self->pings, '-q','-B1','-r1',
  		    @params,
                      @{$self->addresses});
      $self->do_debug("Executing @cmd");
--- 124,130 ----

      my @cmd = (
                      $self->binary,
!                     '-C', ($self->pings)+1, '-q','-B1','-r1',						# Add an extra ping
  		    @params,
                      @{$self->addresses});
      $self->do_debug("Executing @cmd");
***************
*** 134,140 ****
          my @times = split /\s+/;
          my $ip = shift @times;
          next unless ':' eq shift @times; #drop the colon
!
          @times = map {sprintf "%.10e", $_ / $self->{pingfactor}} sort {$a <=> $b} grep /^\d/, @times;
          map { $self->{rtts}{$_} = [@times] } @{$self->{addrlookup}{$ip}} ;
      }
--- 137,143 ----
          my @times = split /\s+/;
          my $ip = shift @times;
          next unless ':' eq shift @times; #drop the colon
!         shift @times;											# Junk the first result.
          @times = map {sprintf "%.10e", $_ / $self->{pingfactor}} sort {$a <=> $b} grep /^\d/, @times;
          map { $self->{rtts}{$_} = [@times] } @{$self->{addrlookup}{$ip}} ;
      }

8<----------------------------------------------------------------------

In some circumstances, the results can be striking:

http://www.jubileegroup.co.uk/JOS/misc/less_smoke.png

--

73,
Ged.