Hello again, Has anyone else noticed the ping times increase by a large amount as soon as you change from fping to hobbit ping? On our site ping times to clients were averaging 1.5m and now they are 29.9m.
I have 4.2-alpha-20060502 installed on Solaris 10 and have been updating to the latest snapshot on a fairly regular basis.
Cheers, Alun
On Fri, May 19, 2006 at 05:06:05PM +1200, Alun Watson wrote:
Has anyone else noticed the ping times increase by a large amount assoon as you change from fping to hobbit ping? On our site ping times to clients were averaging 1.5m and now they are 29.9m.
I haven't seen since my initial tests of hobbitping, and that was due to a poorly chosen design for the packet handling. It has never been in one of the hobbitping versions made available to you.
One explanation might be that hobbitping does behave differently from fping. By default, fping pings each host 3 times, and reports the average round-trip time as the result. hobbitping, on the other hand, stops pinging a host as soon as it gets a response back, and reports the round-trip time of just one ping. If this initial ping takes a long time, e.g. due to an ARP request that needs to be performed, it could affect the ping times you see.
Could you grab the latest snapshot, and in your hobbitserver.cfg set
FPING="$BBHOME/bin/hobbitping --responses=3"
This will make hobbitping report the average round-trip time for 3 pings, like fping does. I would be interested to know if that helps, and if it has any other consequences (like hosts being reported as "down" when they are really up).
Regards, Henrik
Henrik Stoerner wrote:
Could you grab the latest snapshot, and in your hobbitserver.cfg set
FPING="$BBHOME/bin/hobbitping --responses=3"
This will make hobbitping report the average round-trip time for 3 pings, like fping does. I would be interested to know if that helps, and if it has any other consequences (like hosts being reported as "down" when they are really up).
I've been fighting a problem with false conn failures in 4.1.2p1 and I thought I'd try hobbitping to see if it helps. I'm not completely sure that I actually switched from fping to hobbitping, though, because I'm still seeing fping-std* files in server/tmp (as a result of "CMD bbtest-net --report --ping --checkresponse --debug" in hobbitlaunch.cfg.). Is fping in the filenames coming from the fping program itself, or are the files named that way b/c hobbit still calls hobbitping 'fping' because of the variable setting in hobbitserver.cfg?
I built hobbitping from today's snapshot, into my server/bin/ directory, and make it suid root (4755, with root:bb ownership). Is there anything else I need to modify?
Thanks, Tom
On Fri, Jun 02, 2006 at 10:51:26AM -0400, Tom Georgoulias wrote:
I've been fighting a problem with false conn failures in 4.1.2p1 and I thought I'd try hobbitping to see if it helps. I'm not completely sure that I actually switched from fping to hobbitping, though, because I'm still seeing fping-std* files in server/tmp (as a result of "CMD bbtest-net --report --ping --checkresponse --debug" in hobbitlaunch.cfg.). Is fping in the filenames coming from the fping program itself, or are the files named that way b/c hobbit still calls hobbitping 'fping' because of the variable setting in hobbitserver.cfg?
Those filenames are built into the bbtest-net utility. I've changed them for the 4.2 version, but you're probably still running the 4.1.2p1 version of bbtest-net.
If you've changed the FPING setting in hobbitserver.cfg to "hobbitping" then you are running hobbitping, not fping. Despite the filenames.
Regards, Henrik
Henrik Stoerner wrote:
I'm not completely sure
that I actually switched from fping to hobbitping, though, because I'm still seeing fping-std* files in server/tmp (as a result of "CMD bbtest-net --report --ping --checkresponse --debug" in hobbitlaunch.cfg.).
Those filenames are built into the bbtest-net utility. I've changed them for the 4.2 version, but you're probably still running the 4.1.2p1 version of bbtest-net.
I am. All I did was drop the new hobbitping binary in place and make the config file change.
Hobbitping is certainly faster than fping. My conn charts showed an immediate, persistent drop in connection times. Excellent.
Tom
participants (3)
-
Alun.Watson＠fp.co.nz
-
henrik＠hswn.dk
-
tomg＠mcclatchyinteractive.com