From: bert hubert <ahu@ds9a.nl>
To: Shekhar Kshirsagar <shekhark@juniper.net>
Cc: Networking Team <netdev@oss.sgi.com>
Subject: Re: 2.6 IPSec Throughput puzzle
Date: Wed, 29 Dec 2004 13:12:00 +0100 [thread overview]
Message-ID: <20041229121200.GA12199@outpost.ds9a.nl> (raw)
In-Reply-To: <EF311E6F9B0B0848A49ED20B06E9CB27031FDE77@gluon.jnpr.net>
On Tue, Dec 28, 2004 at 07:17:26PM -0800, Shekhar Kshirsagar wrote:
> I'm really puzzled with the performance results I'm getting. The
> performance drop with AH seems high, but worst is performance drop with
> null-esp in transport mode. Another strange observation is that DES
> throughput is greater than null encryption throughput.
Thanks for doing these benchmarks! I did some myself some time ago, but my
hardware isn't representative of anything (consisting of a pentium pro 200
against a P3 1GHz).
> Throughput without IPSec : 936 MBits/s ( 25% CPU Util)
> Transport mode AH - SHA1 : 398 MBits/s (100% CPU Util)
> Transport mode ESP - null/SHA1: 62 MBits/s (100% CPU Util)
> Transport mode ESP - des/SHA1 : 111 MBits/s (100% CPU Util)
> Transport mode ESP - 3des/SHA1: 54 MBits/s (100% CPU Util)
> Transport mode ESP - aes/SHA1 : 192 MBits/s (100% CPU Util)
>
> Do these numbers sound reasonable?
> (I don't have any iptable rules)
It is very easy to use oprofile these days, I suggest you profile for a bit,
should easily tell you what the culprit is. 62MBit/s sounds very low.
Good luck!
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-12-29 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 3:17 2.6 IPSec Throughput puzzle Shekhar Kshirsagar
2004-12-29 12:12 ` bert hubert [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-29 23:50 Shekhar Kshirsagar
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=20041229121200.GA12199@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=netdev@oss.sgi.com \
--cc=shekhark@juniper.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).