Hi Ishita,
I am also same facing problem. Can you please let me know if you find any
solution.
Best Regards,
Tushar.
Date: Tue, 12 Apr 2011 22:09:39 -0400
From: ishim...@gmail.com
To: users@httpd.apache.org
CC: traw...@gmail.com
Subject: Re: [users@httpd] Apache is too slow with SSL
22:09:39 -0400
From: ishim...@gmail.com
To: users@httpd.apache.org
CC: traw...@gmail.com
Subject: Re: [users@httpd] Apache is too slow with SSL
Hi Jeff,
SSL session cache is utilized maximum as out of 3 requests 29850
requests was served as session reuse during my stress test
Hi Jeff,
SSL session cache is utilized maximum as out of 3 requests 29850
requests was served as session reuse during my stress test
Thanks
On Fri, Apr 8, 2011 at 10:06 AM, Jeff Trawick traw...@gmail.com wrote:
On Wed, Apr 6, 2011 at 11:09 PM, Ishita Kapadiya ishim...@gmail.com wrote:
Hi
Thanks Mark
- Put an SSL-terminating appliance in front of your web server. This could
help, especially if the appliance does much of its work in specialized
hardware.
this is the only solution I can see as of now. I am really surprised
that Apache is not handling SSL requests efficiently!
On Wed, Apr 6, 2011 at 11:09 PM, Ishita Kapadiya ishim...@gmail.com wrote:
Hi Jeff,
both ab and JMETER is using keep alive.
keepalive and reusing SSL sessions isn't the same thing
reusing the SSL session (avoiding the expensive part of the handshake)
deals with what happens when the client
On April 6, 2011 0:12 , Ishita Kapadiya ishim...@gmail.com wrote:
I tried to test apache with stress test using JMETER and
results are not really good compared to sun one web server 6.1 running
on the same machine.
i guess worker mpm should work better than prefork..right? I didn't
try
On Thu, Mar 31, 2011 at 7:56 AM, Mark Montague m...@catseye.org wrote:
On March 30, 2011 19:44 , Ishita Kapadiya ishim...@gmail.com wrote:
Hi Mark,
Thanks for your suggestion. I tried below settings in httpd.conf -
IfModule ssl_module
#SSLRandomSeed startup builtin
#SSLRandomSeed
Hi Jeff,
both ab and JMETER is using keep alive. I am using SSL session cache
in the config as -
SSLSessionCacheshmcb:/path to logs/ssl_scache(512000)
Even if so, it is worth using mod_ssl tracing to confirm that the
combination of client/server behavior results in a reasonably high
Hi Mark - I tried to test apache with stress test using JMETER and
results are not really good compared to sun one web server 6.1 running
on the same machine. ab results is good now (after I have used -k
option a suggested by you)
Apache jmeter test output -
count average min max
On March 30, 2011 19:44 , Ishita Kapadiya ishim...@gmail.com wrote:
Hi Mark,
Thanks for your suggestion. I tried below settings in httpd.conf -
IfModule ssl_module
#SSLRandomSeed startup builtin
#SSLRandomSeed connect builtin
SSLRandomSeed startup file:/dev/urandom 1024
SSLRandomSeed connect
Thanks Mark. It really helps. Once I have used keep alive in
benchmark response time reduced from 1900ms to 5 ms!
It should have come to my mind before. But thanks for your valuable
hints.. I can now breath :)
Next thing I am targetting is to use this server for stress test and
will let you know
As subject specifies, I have problem with running Apache on SSL only.
I tried to use 'ab' and tested port 80 443 both. port 80 is too fast
than running the server with port 443.
SSL needs a source of random data. What source have you told Apache to
use? Note that it is possilble that
Hi,
I am not sure whether the problem i am going to describe had been
already faced by someone? At least I tried to look into google and
httpd mail archives but didn't get much help, so I am writing this
mail.
I am running apache 2.2.17 on Linux 2.6.18-128.el5 with 16 Intel Xeon
E7440 @ 2.40GHz
13 matches
Mail list logo
