Having written FTP clients in Java, and now protocol clients using libCurl,
and
I can attest that IIS FTP servers (configured out of the box) are
notoriously slow.

I've witnessed this with IIS3 and IIS4.

Hope this helps.

Cheers, Mike

-----Original Message-----
From: Daniel Stenberg [mailto:daniel_at_haxx.se]
Sent: Tuesday, June 04, 2002 3:57 PM
To: Avery Fay
Cc: libcurl Mailing list
Subject: Re: Bug in libcurl in multithreaded program

On Tue, 4 Jun 2002, Avery Fay wrote:

> On windows with an http url (server is localhost running IIS5):
>
> Retrieved 534768128B in 12 seconds at a rate of 44564010B/s
>
> On windows with an ftp url (server is localhost running IIS5):
>
> Retrieved 534768128B in 619 seconds at a rate of 863922B/s
>
> Also, I have tried the same test with IIS5 on a different machine and
> results are similar (but a lot slower since the program is limited by
100Mb
> ethernet).

The major parts of the source code involved when retrieving these files are
*identical* for both protocols. The HTTP code has some initial headers and
the FTP has an initial command-response phase, but the the actual file is so
terribly huge and both protocols are downloaded using the *exact* same code
sequence.

Have you performed any other measurements using other tools on these
platforms? Can't it just be the fact that IIS serves FTP files a lot worse?

Can you try to use the Linux version to fetch the HTTP and FTP files off the
IIS server and see if you can see any speed difference? I mean when used on
the local network.

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm