Re: [naviserver-devel] Cache compiled Tcl page bytecode

[Andrew P. <at...@pi...>]

On Thu, Jul 13, 2006 at 08:44:17PM +0100, Stephen Deasey wrote:

> Byte code can only be cached per-interp and our caches are
> server-wide.  Currently, it's just caching the read of the Tcl source
> from disk.

I thought the way Rob Mayoff's original feature worked was that it
"compiled" *.tcl pages to Tcl procs, then cached the compiled bytecode
of those procs, presumably in per-thread caches.  Does that sound
right?

What happens for ordinary Tcl procs in ordinary Naviserver Tcl
libraries?  When do they get compiled to bytecode, and how does
Naviserver avoid constantly recompiling them?

Btw, is the byte code for a given Tcl snippet actually different
somehow for Tcl interps in different conn threads?

> I think the way to go here is to merge Tcl pages in with the ADP page
> code.  What's the difference between an ADP page like this:

What would that accomplish?  Is there already cacheing of the
bytecodes of Tcl source included in ADP pages?

> The ADP stuff in aolserver 4.5 has *output* caching.  Tcl pages would

Huh?  Caching of the output generated by Tcl code is totally different
than cacheing the compiled Tcl bytecodes.  Both are useful, neither is
a replacement for the other.

-- 
Andrew Piskorski <at...@pi...>
http://www.piskorski.com/