On 2003.08.13, Elizabeth Thomas <[EMAIL PROTECTED]> wrote: > We have a server that loads in a great deal of tcl - so much so that the > resulting init script is 6.6M in size and contains over 9900 procs. > [...] > > 1. Is there any way to reduce the time to initialize an interp? > (besides the obvious, but not necessarily feasible, option of reducing > the procs that are loaded). Has anyone seen similar behavior and have > some insight into it?
Is there any chance to do further profiling? Where are we losing most of our time? I imagine it has a lot to do with allocating 6.6M of memory for the init script, filling it with the script, then telling Tcl to go parse and execute it. I think the biggest win would be to try and figure out how to get Tcl to bytecode compile the init script, then push that bytecode from the master interp into the new slave interps as they get created. Cut out the entire parse/bytecode compile steps. Perhaps someone who knows and understand those intricate details of Tcl 8.4 can speak up? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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.
