Re: Perl system command memory usage in threads

Question 2: For methods 1 and 3, why do i need to synchronize them? If I do not, the script just hangs up usually after only a few seconds.

I can confirm this problem. I believe it to be a bug in Perl. I think it is to do with the implementation of the wait/waitpid emulation on windows which limits the number of concurrent child processes to 64. I'll try to tie that down a bit further tomorrow and raise a perlbug for it if I succeed.

Meanwhile, on the basis of what I've seen of your code, you should probably try MCE for this task.

Anyone got any experience of this phone's predecessor?

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

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

"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)

In the absence of evidence, opinion is indistinguishable from prejudice.

I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!

Comment on Re: Perl system command memory usage in threads

Replies are listed 'Best First'.
Re^2: Perl system command memory usage in threads by rmahin (Scribe) on Jul 31, 2015 at 23:12 UTC
Awesome, glad this one wasn't just me! Again, this problem also seemed to clear up int 5.20, so maybe its been fixed? Or at least masked a bit better :P That MCE sounds really intriguing. In the full scale version of my code I make use of Thread::Queue and a pool threads (as you have taught me over the years), in your experience how large are the performance/reliability benefits of using MCE over such a model? Thanks!	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.