From owner-freebsd-current Sat Jan 8 0:57:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from void.dynip.com (hobax1-220.dialup.optusnet.com.au [198.142.190.220]) by hub.freebsd.org (Postfix) with ESMTP id 44DDF14D6D for ; Sat, 8 Jan 2000 00:57:03 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id 905B35599; Sat, 8 Jan 2000 19:56:59 +1100 (EST) Message-Id: <4.2.2.20000108193516.00a37800@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 08 Jan 2000 19:56:49 +1100 To: Jason Young From: james Subject: RE: 4.0 slower than 3.4? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:01 8/1/2000 -0600, Jason Young wrote: >Well, several possible issues.. > >It probably isn't the best of all ideas to have BOTH IP firewalling >solutions installed and running at once. This will add some overhead. Pick >one and stick with it. And why do you have DUMMYNET running? I had ipfilter and dummynet in there just to experiment with if i got bored. I haven't even touched or enabled them yet. I just assumed they were disabled unless i did something with them. I had them both in my 3.4 kernel too. >There is a new version of IPFilter in -CURRENT if I recall correctly, and >this may be related to your timing issues. Really you ought to just take >IPFILTER out of your configuration. Ok, i'll try that. Or perhaps i should remove IPFIREWALL. I'm really not too sure on which one i should use.. Do you know which is better? IPFILTER looks more configurable - something i definitely like. >Aside from that, you'll need to use 'top' or some similar utility to find >out where and why you're CPU-bound for FTP transfers. Find out if you're >primarily stuck in the kernel, or if some userland utility is sucking it up >(like natd, but your ipfw rules tend to rule out accidentally running >ethernet traffic through natd). user is around 1-3%, system 50-60%, interrupt 35-45%, idle 0-1%. The only program that has a cpu usage that isn't 0% is ftpd. It climbs up to 25% and then the transfer finishes. I'm only transferring a 25 meg file as i want it to go from the cache on one machine into /dev/null on freebsd to really test the network speed. Cheers >Jason Young >accessUS Chief Network Engineer > > > > -----Original Message----- > > From: james [mailto:death@southcom.com.au] > > Sent: Saturday, January 08, 2000 1:02 AM > > To: freebsd-current@FreeBSD.ORG > > Subject: 4.0 slower than 3.4? > > > > > > > > Hi, > > > > I upgraded a few days ago from 3.4-STABLE to 4.0-CURRENT, and without > > really any change in configuration, anything tcp/ip is much > > slower. Just a > > standard "ping localhost" has gone from ~0.155ms to ~0.195ms. > > Averages for > > "ping -f localhost" have gone from ~0.100ms to ~0.160ms. FTP > > over my lan > > "vr0" has slipped from 7.7MB/s down to 4.8MB/s (!). > > > > I've got hardly anything running on my machine (natd, samba, postfix, > > pppd). 'top' shows 99-100% idle pretty much all the time. > > Load averages are > > all 0.00. CPU usage goes upto 100% during the ftp transfer. > > > > Here's the output of my dmesg: > > > > Copyright (c) 1992-2000 The FreeBSD Project. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All > > rights reserved. > > FreeBSD 4.0-CURRENT #0: Fri Jan 7 00:14:59 EST 2000 > > death@void.dynip.com:/usr/src/sys/compile/DEATH > > Timecounter "i8254" frequency 1193182 Hz > > CPU: Pentium/P54C (166.19-MHz 586-class CPU) > > Origin = "GenuineIntel" Id = 0x52c Stepping = 12 > > Features=0x1bf > > real memory = 33554432 (32768K bytes) > > avail memory = 30040064 (29336K bytes) > > Preloaded elf kernel "kernel" at 0xc028b000. > > Intel Pentium detected, installing workaround for F00F bug > > md0: Malloc disk > > npx0: on motherboard > > npx0: INT 16 interface > > pcib0: on motherboard > > pci0: on pcib0 > > isab0: at device 7.0 on pci0 > > isa0: on isab0 > > ata-pci0: at device 7.1 on pci0 > > ata-pci0: Busmastering DMA supported > > ata0 at 0x01f0 irq 14 on ata-pci0 > > ata1 at 0x0170 irq 15 on ata-pci0 > > vr0: irq 9 at device 18.0 on pci0 > > vr0: Ethernet address: 00:80:c8:d8:19:b7 > > miibus0: on vr0 > > amphy0: on miibus0 > > amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > vga-pci0: irq 11 at > > device 19.0 on pci0 > > ata-isa0: already registered as ata0 > > ata-isa1: already registered as ata1 > > atkbdc0: at port 0x60-0x6f on isa0 > > atkbd0: irq 1 on atkbdc0 > > vga0: at port 0x3b0-0x3df iomem > > 0xa0000-0xbffff on isa0 > > sc0: on isa0 > > sc0: VGA <16 virtual consoles, flags=0x200> > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > > sio0: type 16550A > > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > > sio1: type 16550A > > IP packet filtering initialized, divert enabled, rule-based > > forwarding > > enabled, default to accept, logging limited to 100 > > packets/entry by default > > DUMMYNET initialized (990811) > > IP Filter: initialized. Default = pass all, Logging = enabled > > IP Filter: v3.3.3 > > ad0: ATA-4 disk at ata0 as master > > ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, WDMA2 > > ad2: ATA-0 disk at ata1 as master > > ad2: 1036MB (2121840 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S > > ad2: 16 secs/int, 1 depth queue, WDMA2 > > Mounting root from ufs:/dev/wd0s1a > > > > > > Here's my kernel config: > > > > machine i386 > > cpu I586_CPU > > ident DEATH > > maxusers 64 > > > > options INET > > options FFS > > options FFS_ROOT > > options MSDOSFS > > options PROCFS > > options COMPAT_43 > > options UCONSOLE > > options USERCONFIG > > options VISUAL_USERCONFIG > > options SYSVSHM > > options SYSVMSG > > options SYSVSEM > > > > controller isa0 > > controller pci0 > > > > controller ata0 at isa? port IO_WD1 irq 14 > > controller ata1 at isa? port IO_WD2 irq 15 > > device atadisk0 > > options ATA_STATIC_ID > > options ATA_ENABLE_ATAPI_DMA > > > > controller atkbdc0 at isa? port IO_KBD > > device atkbd0 at atkbdc? irq 1 > > > > device vga0 at isa? port ? conflicts > > > > device sc0 at isa? > > > > device npx0 at nexus? port IO_NPX irq 13 > > > > device apm0 at nexus? disable flags 0x20 > > > > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > > device sio1 at isa? port IO_COM2 irq 3 > > > > controller miibus0 > > device vr0 > > > > pseudo-device loop > > pseudo-device ether > > pseudo-device ppp 2 > > pseudo-device tun 1 > > pseudo-device pty 16 > > pseudo-device md > > > > pseudo-device bpf 4 > > pseudo-device snp 4 > > > > options MD5 > > options PPP_BSDCOMP > > options PPP_DEFLATE > > options PPP_FILTER > > options IPFIREWALL > > options IPFIREWALL_VERBOSE > > options IPFIREWALL_FORWARD > > options IPFIREWALL_VERBOSE_LIMIT=100 > > options IPFIREWALL_DEFAULT_TO_ACCEPT > > options IPDIVERT > > options IPFILTER > > options IPFILTER_LOG > > options IPSTEALTH > > options TCP_DROP_SYNFIN > > options TCP_RESTRICT_RST > > options ICMP_BANDLIM > > options DUMMYNET > > options SOFTUPDATES > > options NSWAPDEV=2 > > options QUOTA > > pseudo-device gzip > > > > > > Here's the first 4 relevant ipfw rules: > > > > 00050 allow icmp from any to any > > 00100 divert 8668 ip from 192.168.1.2 to any out xmit ppp0 > > 00100 divert 8668 ip from any to any in recv ppp0 > > 00200 allow tcp from any to any established > > > > > > I used the same config for 3.4. The only difference is in > > using ata instead > > of wd for my hard drives. And the new miibus controller for > > my ethernet card. > > > > I would've thought that 4.0 would be faster. Is it supposed > > to be? Does > > anybody know of any major difference in 4.0 that would give > > me these speed > > decreases? And possibly how to fix them? > > > > Your help is much appreciated. > > > > Cheers > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message