On Thursday 26 February 2004 11:14, you wrote: > Here I am not sure to understand. Why do your "cleanup" code per request > (the ttrace::cleanup added) delete the loaded functions ? > They should not be deleted... (I am perhaps missing something, I didn't > chek carefully the cleanup code so far). >
Because your code may modify some state during the execution of the procedure and I have to make sure that next run gets a clean interp state. The "regular" way to change the state is to run "ns_eval". So, this was just a means of getting rid of *unwanted* state propagation. > > It looks like that commenting the ttrace::cleanup code is better for the > lock contention problem. If there is a problem with the cleanup, there will > be no need to split storage into several nsv arrays. > > I will try to make tests on our production server with and without the > ttrace::cleanup to see what happens on big load and let you know. > Thanks for your efforts. Nevertheless, I may revert to many-nsv arrays since the cleanup code is sometimes very handy. Zoran -- 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.
