On Thu, 25 Aug 2005, Martin Vogt wrote:

>> 1000 requests in 19 second is extremly slow indeed. Doesn't a network
>> trace (or similar) reveal any details? Are the interval times roughly
>> equal between all requests?
>>
> Here ist the output from the program:

I'm sorry, was that an answer to my question? If so, then I don't understand
it.

>> From the ab.c source there is a comment like:
> #ifdef SIGPIPE
> apr_signal(SIGPIPE, SIG_IGN); /* Ignore writes to connections that
> * have been closed at the other
> end. */
> #endif
>
> Maybe this needs some investigation.

I don't think so. libcurl has equivalent code.

> These are the EINPROGRESS errors:
>
>> socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 32
>> fcntl64(32, F_GETFL) = 0x2 (flags O_RDWR)
>> fcntl64(32, F_SETFL, O_RDWR|O_NONBLOCK) = 0
>> connect(32, {sa_family=AF_INET, sin_port=htons(80),
> sin_addr=inet_addr("192.168.
>> 9.2")}, 16) = -1 EINPROGRESS (Operation now in progress)

This is quite expected. It is caused by non-blocking connects not getting
connected immediately.

Using strace -tt might be interesting.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html