Date: Mon, 30 Nov 1998 11:46:19 -0800 (PST) From: Tom <tom@uniserve.com> To: "WALCZAK, Stan" <swalczak@shl.com> Cc: "'freebsd-stable@FreeBSD.ORG'" <freebsd-stable@FreeBSD.ORG> Subject: Re: output of ping command looks mysterious Message-ID: <Pine.BSF.4.02A.9811301141450.127-100000@shell.uniserve.ca> In-Reply-To: <199811301913.MAA18068@docws002.shl.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Nov 1998, WALCZAK, Stan wrote: > Our network environment: > Dell model Dimension XPS D333 pentium-II 333Mhz 4.5 GIG IBM ultra wide SCSI > HD, ADAPTEC 2940UW controller, BIOS Phenix 4.0 release 6.0, 3-COM 905 TX > network card, 8 MB Video Card AGP 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0 > this machines runs Apache Server 1.3, Qmail and Radius 2.3 > Pipline 75 - original bios from 1996 You should upgrade it. It probably has known bugs. I'm assuming that this is your primary Internet connection > Portmaster 2e - ComOS 3.7.2 > Output of the ping command looks like: > 64 bytes from 142.77.1.1: icmp_seq=20 ttl=250 time=79.736 ms > 64 bytes from 142.77.1.1: icmp_seq=21 ttl=250 time=49.781 ms > 64 bytes from 142.77.1.1: icmp_seq=22 ttl=250 time=993.792 ms > 64 bytes from 142.77.1.1: icmp_seq=23 ttl=250 time=795.402 ms > 64 bytes from 142.77.1.1: icmp_seq=24 ttl=250 time=338.294 ms > 64 bytes from 142.77.1.1: icmp_seq=25 ttl=250 time=94.049 ms > 64 bytes from 142.77.1.1: icmp_seq=26 ttl=250 time=275.623 ms > 64 bytes from 142.77.1.1: icmp_seq=27 ttl=250 time=359.182 ms > 64 bytes from 142.77.1.1: icmp_seq=29 ttl=250 time=412.320 ms > 64 bytes from 142.77.1.1: icmp_seq=30 ttl=250 time=223.237 ms > 64 bytes from 142.77.1.1: icmp_seq=31 ttl=250 time=127.166 ms > 64 bytes from 142.77.1.1: icmp_seq=32 ttl=250 time=687.519 ms > 64 bytes from 142.77.1.1: icmp_seq=34 ttl=250 time=578.269 ms > 64 bytes from 142.77.1.1: icmp_seq=35 ttl=250 time=149.857 ms > 64 bytes from 142.77.1.1: icmp_seq=36 ttl=250 time=372.875 ms > 64 bytes from 142.77.1.1: icmp_seq=37 ttl=250 time=133.176 ms > 64 bytes from 142.77.1.1: icmp_seq=31 ttl=250 time=127.166 ms > 64 bytes from 142.77.1.1: icmp_seq=32 ttl=250 time=687.519 ms > 64 bytes from 142.77.1.1: icmp_seq=34 ttl=250 time=578.269 ms > 64 bytes from 142.77.1.1: icmp_seq=35 ttl=250 time=149.857 ms > 64 bytes from 142.77.1.1: icmp_seq=36 ttl=250 time=372.875 ms > 64 bytes from 142.77.1.1: icmp_seq=37 ttl=250 time=133.176 ms > 64 bytes from 142.77.1.1: icmp_seq=38 ttl=250 time=216.877 ms > 64 bytes from 142.77.1.1: icmp_seq=39 ttl=250 time=504.699 ms > 64 bytes from 142.77.1.1: icmp_seq=40 ttl=250 time=709.457 ms > 64 bytes from 142.77.1.1: icmp_seq=41 ttl=250 time=532.827 ms > 64 bytes from 142.77.1.1: icmp_seq=42 ttl=250 time=261.998 ms > 64 bytes from 142.77.1.1: icmp_seq=43 ttl=250 time=186.549 ms > --- ns.uunet.ca ping statistics --- > 44 packets transmitted, 42 packets received, 4% packet loss > round-trip min/avg/max/stddev = 46.531/249.858/993.792/242.634 ms > > For me it's looks suspicious. Any suggestions why there are jumps up to > 993.792 ms ? Too much traffic? As traffic spikes hit your ISDN link, latency will jump. > The other issue (maybe related) is memory avaialbe, here is output from > vmstat -m command: You are probably misinterpreting these results. Many of these are kernel objects, stored in kernel memory. You probably care about user memory. You don't seem to mention how much total RAM is in your system, but check "swapinfo" to make sure that you aren't using too much swap. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02A.9811301141450.127-100000>