Am 19.01.2011 um 19:18 schrieb Karl Lehenbauer: > 3. Apache children inheriting a preloaded interpreter from the parent > Apache process > > This is unrelated to separate virtual interpreters -- this is for the > production website. When we graceful a production webserver we take it out > of the load balancer first. When we start 200 httpd processes and each one > loads 468 packages, it's not pretty. There is a lot of lock contention in > FreeBSD while these processes all bang on the same package directories, > something we don't totally understand. (This is much faster with ZFS, once > tuned, btw.) 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.]
Doesn't AOLserver do something like that for its cloned interpreter threads (like: https://bitbucket.org/aolserver/aolserver/src/2aa0f24395ae/nsd/tclinit.c) ? So for threaded Apache workers it should be doable. And at least for Java there were some experiments to apply it to cloning initialized jvm processes: http://portal.acm.org/citation.cfm?id=1254812 Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
