netdev
[Top] [All Lists]

Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000

To: Dave Hansen <haveblue@xxxxxxxxxx>
Subject: Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000
From: Nivedita Singhvi <niv@xxxxxxxxxx>
Date: Fri, 6 Sep 2002 09:21:23 -0700
Cc: "Martin J. Bligh" <Martin.Bligh@xxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, hadi@xxxxxxxxxx, tcw@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <3D78CBF6.10609@xxxxxxxxxx>
References: <20020905.235159.128049953.davem@xxxxxxxxxx> <46202575.1031297360@[10.10.2.3]> <3D78CBF6.10609@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) 3.0
Quoting Dave Hansen <haveblue@xxxxxxxxxx>:

> No, no.  Bad Martin!  Throughput didn't drop, "Specweb compliance"
> dropped. Those are two very, very different things.  I've found that
> the server can produce a lot more throughput, although it doesn't
> have the characteristics that Specweb considers compliant.  
> Just have Troy enable mod-status and look at the throughput that
> Apache tells you that it is giving during a run.  
> _That_ is real throughput, not number of compliant connections.

> _And_ NAPI is for receive only, right?  Also, my compliance drop
> occurs with the NAPI checkbox disabled.  There is something else in
> the new driver that causes our problems.

Thanks, Dave, you saved me a bunch of typing...

Just looking at a networking benchmark result is worse than
useless. You really need to look at the stats, settings,
and the profiles. eg, for most of the networking stuff:

ifconfig -a 
netstat -s
netstat -rn
/proc/sys/net/ipv4/
/proc/sys/net/core/

before and after the run. 

Dave, although in your setup the clients are maxed out,
not sure thats the case for Mala and Troy's clients. (Dont
know, of course). But I'm fairly sure they arent using
single quad NUMAs and they may not be seeing the same
effects..

thanks,
Nivedita


<Prev in Thread] Current Thread [Next in Thread>