Here is a snippet. I introduced a 30ms delay and it seems work. But this
is not the best thing to do; especially in my case. I have commented out
the sleep part in the snippet.
opendir DIR, $temp_local_dir;
$ftpobj -> cwd ("$server_root_dir/$DBNAME") or die
"Cannot access this directory\n";
#$ftpobj -> cwd ("$DBNAME") or die "Cannot access this
directory\n";
while ($filename = readdir(DIR)) {
if($filename =~ /.xls/ && $filename =~
/$DBNAME/){
$ftpobj ->
put("$temp_local_dir/$filename");
$counter = $counter+1;
#$microseconds = 30_000;
#$actualslept = usleep $microseconds;
}
}
Some of the files I am transferring are very small. I think because of
that the perl FTP module over runs the capability of the IIS FTP server.
The files I am referring here have size less than 1 kb and there might
be about 150 of them. Any thoughts?
Manish
-----Original Message-----
From: $Bill Luebkert [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 30, 2005 7:08 PM
To: Mittal, Manish
Cc: [email protected]
Subject: Re: Perl NET::FTP limitations
Mittal, Manish wrote:
> Does anyone know of a limitation of the NET::FTP module? I am using
this
> module to copy about 1 GB worth of data in about 1300 files. After
> successfully transferring about 650 files, the transfer becomes
> painfully slow (it takes about an hour for the rest and sometimes
more)
>
> Some info that might be useful
>
> 1- 100 Mbps, full duplex network.
>
> 2- FTP server and client both on the same internal network.
>
> 3- The transfer has worked like a charm for lower number of
files.
>
> Let me know if you need more info.
Yes - we do. You may be causing it by over-using resources. A code
snippet should help. Trim it as best you can and test it to see if
it reproduces the problem after trimming.
_______________________________________________
ActivePerl mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
