moving to a new thread on dev@, which is probably the better place to do this :)
Stas Bekman wrote:
Geoffrey Young wrote:
[...] in the meanwhile I'll see if I can't prototype a perl interface for killing both processes and interpreters.
I'd suggest discussing this before spending any time prototyping things. I can't quite see how are you going to kill interpreters and how are you going to make the decision which one to kill. You don't want to kill an interpreter you are in, because you have no idea whether it's one that is of the biggest size. The idea was to have an garbage collection thread which will kick in when the size of the process goes beyond the limit and measure the idle interpreters in the pool and kill the big ones. Or do you have something else on your mind?
yeah, I don't know how to handle it. as I mentioned back in vegas, I don't see the reason for killing off interpreters - the process is really the only thing you can measure, so once it gets too large probably the best way is to kill it gracefully and let another one spawn in its place. there were some other things we discussed (such as a two-tiered limit, where the first tier knocks off an interpreter, while the next tier knocks off the process) but I'm not sure if that is realistic or not.
certainly, just limiting the process as a whole is easier to implement for the reasons you just listed, and I'm content to leave it at that. everyone else seemed to want the thread-killing api, though...
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
