From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Linux router performance
Date: Thu, 01 Jun 2006 02:03:29 +0000 [thread overview]
Message-ID: <447E4AF1.3050009@gmx.net> (raw)
In-Reply-To: <004e01c684dc$3dfc3c10$303d5854@cttc.es>
Alexander Samad wrote:
> On Thu, Jun 01, 2006 at 02:44:57AM +0200, Carl-Daniel Hailfinger wrote:
>> Damjan wrote:
>>>>> I wonder about the performance of a Linux box used as router (I guest I'm
>>>>> not the first :). Althought I know it mainly depends on the hardware, I'm
>>>>> trying to find some references on the topic or comparations with other
>>>>> routing solutions (FreeBSD box used as router, Cisco, etc). For example,
>>>>> http://facweb.cti.depaul.edu/jyu/Publications/Yu-Linux-TSM2004.pdf
>>>>> (althought is related with Linux-briding more than with Linux-routing) shows
>>>>> in Figure 14 that with an AMD Duron 1.3GHz 512M RAM a throughput of 90 Mbps
>>>>> can be achieved.
>>>> On an AMD Athlon64 3200+ (2 GHz) I was able to saturate 2 PCI-Express
>>>> gigabit cards (but that was with 1500 byte packets). Never tried more
>>>> although the box has 6 interfaces capable of gigabit, 4 of them attached
>>>> via PCI-Express.
>>> But that's _only_ 83333 packets/s isn't it.
>> Hm. How do you arrive at that result? I get twice the numbers.
>> nic a: 1 gbit in -> nic b: 1 gbit out
>> nic b: 1 gbit in -> nic a: 1 gbit out
>> total 2 gbit
>> 2 gbit /(1500*8 bit/frame) ~ 160k packets/s
>>
>> Please note that I did not test with smaller frame sizes, so 1Mp/s
>> may be possible (I'll test that if I have some spare time).
>
> what if you test inbound and outbound at the same time - the cards
> should be capable of full duplex ?
I tested 1 gbit in and 1 gbit out per nic at the same time. That's
how I arrived at my results.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-06-01 2:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 18:01 [LARTC] Linux router performance Fermín Galán Márquez
2006-05-31 20:27 ` Andreas John
2006-05-31 23:24 ` Carl-Daniel Hailfinger
2006-06-01 0:34 ` Damjan
2006-06-01 0:44 ` Carl-Daniel Hailfinger
2006-06-01 1:59 ` Alexander Samad
2006-06-01 2:03 ` Carl-Daniel Hailfinger [this message]
2006-06-01 2:21 ` Alexander Samad
2006-06-01 4:52 ` Carl-Daniel Hailfinger
2006-06-01 8:46 ` Andrew Lyon
2006-06-01 11:23 ` Ronny Aasen
2006-06-01 11:46 ` Carl-Daniel Hailfinger
2006-06-01 20:33 ` Jesper Dangaard Brouer
2006-06-10 6:45 ` S Mohan
2006-06-16 7:52 ` Tomas Bonnedahl
2006-06-16 8:23 ` [LARTC] Linux router performance (fwd) Jesper Dangaard Brouer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=447E4AF1.3050009@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.