From: "Imran Badr" <imran.badr@cavium.com>
To: "'Roland Dreier'" <roland@topspincom.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Linux kernel 2.4 and TCP terminations per second.
Date: Tue, 6 Nov 2001 16:02:44 -0800 [thread overview]
Message-ID: <018201c1671f$877cba70$3b10a8c0@IMRANPC> (raw)
In-Reply-To: <521yjb5utz.fsf@love-boat.topspincom.com>
I am not worried about SSL handshakes/sec. I am looking forward to how much
http/sec I could extract out of a moderate linux box. I have a dell box with
PIII 800 MHz, 256 MB RAM running a very light weight server (which I wrote)
and I wanted to find out how much time does it spend in system for TCP
terminations. The system in running linux kernel version 2.4.2
The server sits in a loop and launches worker threads as it receives a tcp
socket connection. The worker thread then sits in an infinite loop and
sends/receives data from client (which is again a custom client).
I figured out that most of the CPU time was spent in the kernel mode for TCP
terminatiions and Network was not the bottleneck.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Roland Dreier
Sent: Tuesday, November 06, 2001 3:44 PM
To: imran.badr@cavium.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux kernel 2.4 and TCP terminations per second.
Imran> I am running openssl with apache using modssl. I will have
Imran> to look at whether could I use openssl with TUX or zeus.
If you are doing SSL termination without a hardware crypto accelerator
then the cost of the public key operations for the SSL handshake will
far outweigh the cost of TCP termination and the webserver. With a
typical machine (say a 1 GHz P3) I would estimate you could do 200 SSL
handshakes/sec with apache/modssl (with 95% of your CPU time spent in
OpenSSL RSA code). With a hardware crypto accelerator you could get
up to 600-1000 handshakes/sec but the crypto will still be the
bottleneck.
Roland
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-11-07 0:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-30 22:31 [CFT][PATCH] cleanup of partition code Alexander Viro
2001-09-30 23:28 ` Tom Rini
2001-10-01 1:57 ` Alexander Viro
2001-10-01 6:54 ` Anton Altaparmakov
2001-11-06 20:25 ` Linux kernel 2.4 and TCP terminations per second Imran Badr
2001-11-06 23:22 ` Alan Cox
2001-11-06 23:34 ` Imran Badr
2001-11-06 23:43 ` Roland Dreier
2001-11-07 0:02 ` Imran Badr [this message]
2001-11-06 23:56 ` David Lang
2001-11-07 0:29 ` Alan Cox
2001-10-01 11:40 ` [CFT][PATCH] cleanup of partition code Alexander Viro
2001-10-01 4:22 ` Erik Andersen
2001-10-01 5:27 ` Alexander Viro
2001-10-01 6:04 ` Erik Andersen
2001-10-01 6:48 ` Alexander Viro
2001-10-01 8:03 ` Alexander Viro
2001-10-01 9:06 ` Nick Craig-Wood
2001-10-01 21:11 ` Alex Bligh - linux-kernel
2001-10-01 23:15 ` Erik Andersen
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='018201c1671f$877cba70$3b10a8c0@IMRANPC' \
--to=imran.badr@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspincom.com \
/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