On Tue, Jul 13, 1999, Jeffrey Burgoyne wrote:
> > > [...]
> > > Yes, when you specify where to put SSL session cache and use MM you must
> > > specify size of MM pool as well. You do not want it really big.
> >
> > And on some platforms you not even _can_ make it very large, because of
> > restrictions of the underlaying shared memory implementation! But MM and
> > mod_ssl check this, so don't worry to much about this. A cache of 512 KB is
> > usually fine.
>
> Any limit on Dec Alpha as to how big it can be? Politics be what they may,
> I'm trying to convince a group to rewrite one of their CGI's as it takes
> 120 Meg of memory when its runs (and its written in C). Their reason for
> not rewriting is that we generally have 300 megs free memory on the
> server, so whats the big deal?
Look at the output of MM when you run it's configure. It tries to determine
the upper limit for a shared memory segment. On most mmap(2) based systems
it's at least more than 32MB. Usually no real limit up to 2GB. On other where
SysV IPC is used you get limits in the range of 1(!) MB and 32MB. A usual SSL
session has less than 1KB. So even with just a 512 KB cache and a reasonable
expiry time you can cache a lot. But when you have lots of HTTPS traffic you
can increase this, 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]
