From owner-freebsd-performance@FreeBSD.ORG Fri Mar 24 16:03:33 2006 Return-Path: X-Original-To: freebsd-performance@freebsd.org Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6033F16A41F for ; Fri, 24 Mar 2006 16:03:33 +0000 (UTC) (envelope-from luke@foolishgames.com) Received: from mail.foolishgames.com (mail.foolishgames.com [206.222.28.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C1AB43D55 for ; Fri, 24 Mar 2006 16:03:31 +0000 (GMT) (envelope-from luke@foolishgames.com) Received: from [192.168.0.151] (24-176-2-209.dhcp.klmz.mi.charter.com [24.176.2.209]) (authenticated bits=0) by mail.foolishgames.com (8.13.5/8.13.3) with ESMTP id k2OG3Hmp050176 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Fri, 24 Mar 2006 11:03:20 -0500 (EST) (envelope-from luke@foolishgames.com) X-Habeas-Swe-9: mark in spam to . X-Habeas-Swe-6: email in exchange for a license for this Habeas Content-Transfer-Encoding: 7bit X-Habeas-Swe-3: like Habeas SWE (tm) Date: Fri, 24 Mar 2006 11:06:11 -0500 X-Priority: 3 X-Habeas-Swe-8: Message (HCM) and not spam. Please report use of this X-Habeas-Swe-5: Sender Warranted Email (SWE) (tm). The sender of this From: Lucas Holt X-Habeas-Swe-2: brightly anticipated In-Reply-To: <003301c64f44$89fdcd40$0201a8c0@oxy> References: <20060322071023.70808.qmail@web30305.mail.mud.yahoo.com> <442187FE.3060300@lbl.gov> <003301c64f44$89fdcd40$0201a8c0@oxy> To: OxY X-Habeas-Swe-7: warrant mark warrants that this is a Habeas Compliant Mime-Version: 1.0 (Apple Message framework v746.3) X-Habeas-Swe-4: Copyright 2002 Habeas (tm) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed X-Habeas-Swe-1: winter into spring Message-Id: <820F5FD6-C31F-4C28-9E66-64643C03086B@foolishgames.com> X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on mail.foolishgames.com X-Virus-Status: Clean Cc: "Jin Guojun \[VFFS\]" , FreeBSD Mailing Lists , Gary Thorpe , Arne Woerner Subject: Re: packet drop with intel gigabit / marwell gigabit X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Mar 2006 16:03:33 -0000 On Mar 24, 2006, at 8:12 AM, OxY wrote: > hi guys! > > well, i changed my motherboard and CPU from the > asus a7v8x+amd 2000+ xp to > the abit be7 + p4 2.4 (533fsb) and the packet loss fell down from > 8% to 2%, but > still have loss... > loss coming when i have load.. i guess it decreased because of the > bigger resources. > still waiting for tipps, hints, everything :) > > I don't think you'll ever get down to 0% in your situation. I noticed in the initial post that you have net.inet.tcp.inflight.enable=1 set. On my home network, turning that off helped a great deal with samba traffic to my freebsd file server/ router. It didn't seem to affect traffic to my webserver much, but its very low traffic. The problem with tuning on other people's settings is that each workload is different though. There might not be a miracle hack to get this working how you want. I'm sure the new box is a bit better as I attempted some of the steps outlined by Jin on my two machines. (amd 2300+ w/ msi nforce2 512mb ram and P4 2.4ghz 1gb ram 533mhz fsb) The P4 system was faster on all my tests by quite a large margin. I can't remember what version of FreeBSD you are using, but I do know they've done work on the em and fxp drivers during the 6.x series. I noticed a big improvement from 5.4 to 6.0 release and to 6.1 betas from 6.0 release. You might have better luck when 6.1 release comes out. I must admit, I didn't follow all of Jin's calculations. I do think he's right about some motherboard chipsets having limitations that limit real world traffic on the bus though. It follows what I learned in college during electrical engineering courses I was required to take. Hardware and Software are a lot alike. Just because something claims to support specific performance characteristics, does not mean that it does. Windows is a great example. I would guess that your problem is a combination of several factors including hardware, software, and network conditions. Almost every time I've had a problem like this at work or home its been a wiring problem or a switch limiting the throughput. Lucas Holt Luke@FoolishGames.com ________________________________________________________ FoolishGames.com (Jewel Fan Site) JustJournal.com (Free blogging) FoolishGames.net (Enemy Territory site)