in reply to Re^4: Win32 and threads;
in thread Win32 and threads;

There is (currently) a limit of 120 threads per process (on win32/5.8.4/XP/my computer/11th July 2004/SE UK etc :). This is not a hard-wired limit within perl and may vary with build.

That you are not seeing any error message suggests that your installation is not configured to report segfaults. There is an option to "Send Administrative Alert" in Control panel->System->Advanced->Startup and Recovery->Settings->System failure. At least that's where it is on XP.

That perl is not detecting the underlying problem and reporting it's own message is a bug. I have tracked down the unchecked API call and will submit a perlbug with the information.

However, if you can show me a useful application of using more than half a dozen or so simultaneous threads, I'll show you a better way :)

Update: Perlbug # 30674.


Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

Replies are listed 'Best First'.
Re^6: Win32 and threads;
by pbeckingham (Parson) on Jul 11, 2004 at 20:22 UTC

    However, if you can show me a useful application of using more than half a dozen or so simultaneous threads, I'll show you a better way :)
    I don't mean to disagree with this - in fact I think you're right, but I would be very interested to read an elaboration on this claim from you. Would you?

      The smiley was intended to defuse the statement from being taken as definitive, but in general, I'll stand by it (in the context of Perl programs using ithreads on Win32).

      But, it's difficult to elaborate upon for the general case. I've yet to see a good use of large numbers of iThreads. And I've yet to find the right way to write the type of application that might make use of large numbers of threads using perl.


      Examine what is said, not who speaks.
      "Efficiency is intelligent laziness." -David Dunham
      "Think for yourself!" - Abigail
      "Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon