>> It takes minutes to settle down before our stuff can put the >> server back into the webserver. What would be incredibly cool would >> be to be able to load up the 468 packages in the parent httpd process >> one time and then have each child process use the same Tcl interpreter >> already loaded with the packages. This would be a way more than >> 200-fold improvement in Apache startup time for us (because it >> would eliminate all the contention.) [I don't even know if this >> is possible.] > > so slave interpreters don't inherit packages loaded in their parent > interp? Getting the answer should be easy...
I don't even think this is possible. You're talking about creating an interp in the parent httpd process and then somehow handing that off to each child as a copy as it's created? I think that's a great idea, but I don't see how to implement it. AOLServer has this idea of cloning interpreters, but they're always working within the same process not multiple children. And I don't even know if THEY clone the entire interpreter, packages and all. I would think they do though if it's a true interp clone. I would love to be proven wrong though. 0-] I don't have near the kind of load you guys are using, but the idea of cloning a full interpreter has been an idea I've wanted for a long time. Cloning within the same process is possible. Cloning in a child? *shrug* D
