I have run across a problem in my local network communications, which should be lightning fast. Here is an example:
#!/idcom/bin/perl
use IO::Socket::INET;
use Time::HiRes qw( gettimeofday tv_interval );
use strict;
our $PORT = 9991;
if(fork) {
my $s = IO::Socket::INET->new( LocalPort => $PORT, Listen => 5, Re
+use => 1 );
my $c = $s->accept();
while(<$c>) {
print {$c} $_;
}
}
else {
sleep 1;
my $s = IO::Socket::INET->new( PeerAddr => 'localhost:'.$PORT );
for(1..5) {
my $t0 = [gettimeofday];
print {$s} "func=mbs_descriptive&type=";
print {$s} "&secid=313627KM2\n";
print ''.<$s>;
print tv_interval( $t0, [gettimeofday] ),"\n";
}
}
OUTPUT
func=mbs_descriptive&type=&secid=313627KM2
0.000458
func=mbs_descriptive&type=&secid=313627KM2
0.040329
func=mbs_descriptive&type=&secid=313627KM2
0.040905
func=mbs_descriptive&type=&secid=313627KM2
0.03986
func=mbs_descriptive&type=&secid=313627KM2
0.040938
now if I change the code to use
print {$s} "func=mbs_descriptive&type=&secid=313627KM2\n";
instead of
print {$s} "func=mbs_descriptive&type=";
print {$s} "&secid=313627KM2\n";
<C>
I then get
<C>
func=mbs_descriptive&type=&secid=313627KM2
0.000448
func=mbs_descriptive&type=&secid=313627KM2
9.3e-05
func=mbs_descriptive&type=&secid=313627KM2
0.000161
func=mbs_descriptive&type=&secid=313627KM2
7.8e-05
func=mbs_descriptive&type=&secid=313627KM2
7.7e-05
A lot of our code kind of piecemeal prints to a socket like this, what is going on, and can I fix it without completely redesigning and existing codebase?
- Ant
- Some of my
best work - (1 2 3)
-
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.
|