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/
-
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/