Re: [AOLSERVER] AOLserver operational issues

[Peter M. Jansson]

On Thursday, September 20, 2001, at 10:53 AM, Lamar Owen wrote:

> My question is: how is AOLserver4 going to handle this?  Is AS4 going to
> throwback to 2.3.3's design in this for performance?  This makes our
> decision
> to stick with 2.3.3 here look more attractive....  Of course, 2.3.3
> had/has
> its own problems, but this one is not one of them.

It's unlikely that AS4 will revert to the shared interpreter model.  Jim
Davidson hacked Tcl 7.x mightily to get it to allow interpreters to be
thread-safe and shareable.  Tcl 8.x specifically requires that a thread
have no more than one interpreter, and no interpreter can be shared across
threads; since AOLserver is moving to Tcl 8.x-only, the shared
interpreters are going away.

Still, that isn't all bad news -- the state maintained for an interpreter
isn't really large, rather the procs (compiled into objects) are the
biggest thing in memory (he writes without the benefit of actually
measuring), so there's hope.

If you run one or two web nsds per machine, you'll definitely win with
AOLserver 3 or 4 -- it just works better, has fewer bugs, and Kriston won'
t yell at you for using obsolete software.