http://qs321.pair.com?node_id=426814


in reply to Re^8: Isolating dynamically loaded modules with Thread::Isolate.
in thread Isolating dynamically loaded modules with Thread::Isolate.

You claim that forks duplicate everything? I think not. At least not on any OS which implements copy on write memory, which would be any semi-current *nix. And in many applications it is OK if communication overhead is slightly more in order to benefit from the saved memory and increased protection.

As for the rest, I haven't tracked to see if people's experience with Perl's threading in the last half year is as bad as it had been before that. It probably has improved, though not to the point where I'd be willing to put it into production. But my general comments about threading remain true, and my specific comments about Perl's thread model in specific are, to the best of my knowledge, accurate. If you have specific examples to change my mind, that would be one thing. But you don't appear to, instead you're just telling me that what I've said is red herrings and wrong, without providing me with any specifics.

Since I feel no need to convince you of anything, and I don't feel that this conversation is going anywhere I'm exiting the conversation here.

  • Comment on Re^9: Isolating dynamically loaded modules with Thread::Isolate.

Replies are listed 'Best First'.
Re^10: Isolating dynamically loaded modules with Thread::Isolate.
by BrowserUk (Patriarch) on Feb 01, 2005 at 06:24 UTC
    instead you're just telling me <<...X...>> without providing me with any specifics.

    That is exactly the problem I have with your posts. It is impossible for me to either counter or agree with non-specific FUD.


    Examine what is said, not who speaks.
    Silence betokens consent.
    Love the truth but pardon error.