in reply to AnyEvent::HTTP usage
in thread Async DNS with LWP

I guess you need to enter an AnyEvent "main loop" and wait for all asynchronous things to finish. See the AnyEvent documentation:

use AnyEvent;
use AnyEvent::HTTP;

my $done = AnyEvent->condvar; # stores whether a condition was flagged

http_get "http://www.google.com/", sub { print $_[1]; $done->send };

$done->recv; # enters "main loop" till $condvar gets ->send

[download]

Even better, you could send yourself the data through the condvar.

Replies are listed 'Best First'.
Re^2: AnyEvent::HTTP usage
by jc (Acolyte) on Oct 05, 2010 at 15:01 UTC
    Thanks, OK. So here's what I've got so far. I've got this thing doing asynchronous HEADs. I'm allowing 10 HEAD requests to be fired off at a time. But, here's the but... it doesn't really seem to be working any faster than an LWP based version forked into 10 processes. Perhaps, you were right Corion. Maybe this is not the kind of optimisation my crawler needs. Any other ideas? 
    #!/usr/bin/perl -w
use strict;
use warnings;
use Data::Dumper;
use AnyEvent::HTTP;

my ($domain,$START_TIME,$MAX_QUERIES,$MAX_QUEUE,$time,$done,$heads);
my (@condvars);

$START_TIME  = time;
$MAX_QUERIES = 10;
$MAX_QUEUE   = 10;
$heads       = 0;

while (1)
{
  # send dns packets
  for my $i (1..$MAX_QUERIES)
  {
    $domain = <>;
    # clean off newline
    chomp $domain;
    my $http_url = "http://www.".$domain;
    my $condvar = AnyEvent->condvar;
    push @condvars, $condvar;
    http_request HEAD => $http_url, sub 
                                 {
                                   #warn Dumper @_;
                                      $condvar->send;
                                 };
  }
  
  while (my $condvar = pop @condvars)
  {
    $condvar->recv;
  }
  
  $done += $MAX_QUERIES;
  $time = time - $START_TIME;
  print "Tried $done domains, $heads headers found in $time seconds.\n
+";
}

    [download]
[reply]
[d/l]

      Maybe you should profile whether your application is network bound, IO-bound or CPU-bound. If it's not maxing out any of these, then the problem is on the opposite end of the network connection. Then you maybe need to launch more (asynchronous) requests. But if they all hit the same server(s), you won't see any improvement there either.

      See Devel::NYTProf for how to find out where your application spends its time. This should usually be the first step.

[reply]

In Section Seekers of Perl Wisdom