Bas Scheffers wrote:
> Olaf Mersmann said:
> > something I discovered and later started to use. There's no question,
> > that if it where possible and feasable to present each conn a "clean
> > plate" that that would be the correct thing to do. In fact, it would
> You'd get PHP, and we all know how blindingly fast that is
> for having a completely clean interpreter every time...
>
> So it's a trade-off, you either get the fastest web-scripting
> implementation in the business, or you get a dummy proof one.
You get much more than a dummy-proof one in Tcl, but it is
important to note that you get a clone of an *AOLServer*
interp, not just a Tcl interp. Clean Tcl interps are cheap:
% time {interp delete [interp create z]} 1000
2312 microseconds per iteration
That's on a 1.8ghz P4 running SuSE 9.2, for reference. In
AOLServer, you do a lot more than create a clean interp, you
initialize it with *gobs* of stuff.
I've mentioned it before, but I'll stress it again - it is
possible to improve this speed, possibly dramatically. If
one were to go into the mod-8-3-4-branch that ActiveState
did for Cisco, you will find some interesting core changes.
One of them is an implementation of Tcl_CloneInterp. That
would likely have a large impact, but it wouldn't be trivial
to port to the head and make thread-safe (est 3-4 weeks).
However, I'm sure that a simple, thorough analysis of the
existing framework would provide enough insight into how to
cut the current startup time down without any C changes as
well. Deferring of tasks, lazy loading, etc.
Jeff
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
