On Fri, Feb 25, 2005 at 12:58:45PM -0500, Dossy Shiobara wrote:

> Zoran's "ttrace" extension might help here, but "ttrace" doesn't give
> you the performance boost of Tcl's parsing and byte compiling on first
> execution, and subsequent executions are just calls into the bytecode.

I'm not sure what you mean there.  I haven't looked at the code, but
my understanding is that ttrace uses the Tcl "unknown" proc to look up
and copy procs from a server-wide store into the local interp, when
each proc is first called.  Thus, you take a performance hit on the
first call of each proc, but from that point onward calling that proc
works exactly the same way as it would in stock AOLserver without
ttrace.  Is that correct?

ttrace looks like a win-win situation to me.  If you want certain
procs pre-loaded into the interp, it should be feasible to add some
sort of ttrace hook to greedily install those procs into every new
interp.  And if you used that hook for ALL procs, every single one,
then you'd basically be back to exactly how stock AOLserver behaves
without ttrace, no?

--
Andrew Piskorski <[EMAIL PROTECTED]>
http://www.piskorski.com/


--
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.

Reply via email to