Where's your sense of commitment! <g>

Seriously, I'm surprised you stuck with me this long. Thanks very much for all the tips.

The "make it work, then make it work fast" principle is what I always work with. Just sometimes you can see "obvious" performance hits that you might as well take out while you're doing it in the first place. ::perl_clone vs ::perl_alloc is just such an instance.

Bad news (for you), I'm going to pick up on your last point. I can easily call a Perl routine always on the *same* thread. How would it then communicate to the thread pool? (See, now look what you've done. I'm starting to learn perl, diving in at the deep end. My wife's not going to be at all happy with you <g>.)

Phil