Using fork (even via Parallel::ForkManager) on Windows, where fork is emulated, doesn't make much sense.
I use this for stress testing my local servers. By default it will run 20 clients, each will make 1000 (serial) connections and exchange 1000 conversations. Adapting it to your needs should be straight forward.
#! perl -slw
use strict;
use threads;
use IO::Socket;
our $W //= 20;
my @t = map{
async {
for( 1 .. rand 1000 ) {
my $s = new IO::Socket::INET(
'localhost:12345'
) or die "Failed to connect to server: $!";
for( 1 .. rand 1000 ) {
print $s "Message $_";
scalar <$s>;
}
close $s;
}
};
} 1 .. $W;
$_->join for @t;
-
-
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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|