On Mon, Jul 12, 1999, Jeffrey Burgoyne wrote:
> After experienceing some "brownouts" in Stronghold SSL, I changed our web
> server to modssl last week. We saw a huge increase in performance (of
> course, the brownouts really dragged down the stats I expect) in the range
> of 50 to 80 percent.
>
> Since our site is a very high profile government site, I tried to keep
> things as simple as possible for the cutover and left out the Shared
> Memory library. I can't find an over abundance of documentation on this
> feature and had some questions.
>
> First off, does the cache apply to all http requests as well as https
> requests. I'm assuming it does, but its not too exact in the
> documentation.
It's a _SSL_ session cache, so it applies only to HTTPS requests, of course.
For HTTP there no real session id.
> Secondly, is there any configuration parameters to allow me to specify how
> much memory it uses. I'm generally running with about 300 Megs free.
SSLSessionCache shm:/path/to/file(bytes)
The "bytes" is what you're searching for.
> Any idea of what performance gain to expect? We get about 15000 real hits
> a day, about 60000 total (including graphics). About 10% of those are SSL.
> I need to justify why we want to make the change to the web server and
> even a rough idea is all my employers need to see.
I've still not seen any benchmarks, but the shared memory based session cache
is certainly a magnitude faster then the disk-I/O dependent DBM based session
cache, of course.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
