[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0903312145130.2954@ask.diku.dk>
Date: Tue, 31 Mar 2009 21:52:13 +0200 (CEST)
From: Jesper Dangaard Brouer <hawk@...u.dk>
To: Eric Dumazet <dada1@...mosbay.com>
Cc: netdev <netdev@...r.kernel.org>, Rick Jones <rick.jones2@...com>
Subject: Re: [PATCH] netfilter: finer grained nf_conn locking
On Mon, 30 Mar 2009, Eric Dumazet wrote:
> Jesper Dangaard Brouer a écrit :
>> On Mon, 30 Mar 2009, Eric Dumazet wrote:
>>
>>> Jesper Dangaard Brouer a écrit :
>>>>
>>>>> Eric Dumazet wrote:
>>>>>> "tbench 8" results on my 8 core machine (32bit kernel, with
>>>>>> conntracking on) : 2319 MB/s instead of 2284 MB/s
>>>>
>>>> How do you achieve this impressing numbers?
>>>> Is it against localhost? (10Gbit/s is max 1250 MB/s)
>>>
>>> tbench is a tcp test on localhost yes :)
>>
>> I see!
>>
>> Using a Sun 10GbE NIC I was only getting a throughput of 556.86 MB/sec
>> with 64 procs (between an AMD Phenom X4 and a Core i7). (Not tuned
>> multi queues yet ...)
>>
>> Against localhost I'm getting (not with applied patch):
>>
>> 1336.42 MB/sec on my AMD phenom X4 9950 Quad-Core Processor
>>
>> 1552.81 MB/sec on my Core i7 920 (4 physical cores, plus 4 threads)
>
> Strange results, compared to my E5420 (I thought i7 was faster ??)
>
>> 2274.53 MB/sec on my dual CPU Xeon E5420 (8 cores)
I tried using "netperf" instead of "tbench".
A netperf towards localhost (netperf -T 0,1 -l 120 -H localhost)
reveals that the Core i7 is still the fastest.
24218 Mbit/s on Core i7 920
11684 Mbit/s on Phenom X4
8181 Mbit/s on Xeon E5420
A note to Rick, the process "netperf" would use 100% CPU time and
"netserver" would only use 70%.
Hilsen
Jesper Brouer
--
-------------------------------------------------------------------
MSc. Master of Computer Science
Dept. of Computer Science, University of Copenhagen
Author of http://www.adsl-optimizer.dk
-------------------------------------------------------------------
Powered by blists - more mailing lists