Re: [perl #129779] Concurrency worse than no concurrency

Am 11.10.2016 um 13:33 schrieb Steve Piner: On Tue, 04 Oct 2016 04:23:54 +1300, Joachim Durchholz via RT wrote: Am 03.10.2016 um 06:34 schrieb Zoffix Znet via RT: Seems the issue has more to do with running an empty loop, rather than performing a real

Re: [perl #129779] Concurrency worse than no concurrency

On Tue, 04 Oct 2016 04:23:54 +1300, Joachim Durchholz via RT wrote: Am 03.10.2016 um 06:34 schrieb Zoffix Znet via RT: Seems the issue has more to do with running an empty loop, rather than performing a real computation. This is a run on a 4-core box.

Re: [perl #129779] Concurrency worse than no concurrency

Am 03.10.2016 um 06:34 schrieb Zoffix Znet via RT: Seems the issue has more to do with running an empty loop, rather than performing a real computation. This is a run on a 4-core box. Attempting to parallelize an empty loop makes the execution 1 second slower: [...] But running actual

Re: [perl #129779] Concurrency worse than no concurrency

But Crypt::Bcrypt seems to be mostly native call stuff. While it is running, I wouldn't imagine that it has much to do with Perl 6 at all. The original case I noticed the problem in was a recursive function; all Perl 6, no IO. Sure, it's not real work, but I'm not at that stage yet. Try

[perl #129779] Concurrency worse than no concurrency

Seems the issue has more to do with running an empty loop, rather than performing a real computation. This is a run on a 4-core box. Attempting to parallelize an empty loop makes the execution 1 second slower: my = { for ^2_000_000 { } }; my $start = now; (^4).map: my $stop = now;

[perl #129779] Concurrency worse than no concurrency

# New Ticket Created by Steve Piner # Please include the string: [perl #129779] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129779 > This could be a stupid user problem, in which case I apologise for wasting your time.