No. It is N times as effective for N identical threads as it is for 1.

No, it's not:

use strict;
use warnings;
use 5.010;
use threads;
use Chart::Clicker;
use Time::HiRes qw(time);
my $N = 32;
my $t = time;
my @thr;
push @thr, threads->create( sub { 1; } ) for 1 .. $N;
$_->join for (@thr);
say time - $t;
[download]

Runs in 5.57 sec.

use strict;
use warnings;
use 5.010;
use threads;
use Time::HiRes qw(time);
my $N = 32;
my $t = time;
my @thr;
push @thr, threads->create( sub { require Chart::Clicker; } ) for 1 ..
+ $N;
$_->join for (@thr);
say time - $t;
[download]

Requires 34 sec to finish

Did you actually read the examples I gave in my post before last?

To summarise:

• If you have an app that has worker threads that don't need Tk, and a main thread that does.

  use any moduels required by the workers; spawn the workers; then require Tk in the main thread.

• Alternatively, it can make sense to spawn a (single) thread that then requires the 'big module' that only it needs; and then require the modules needed by the worker threads before spawning them.

  See the DBI example.

All of this seems pretty clear from my post before last. To arrive at your interpretation on my intent seems hard.

---

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".

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

RIP an inspiration; A true Folk's Guy