I guess libcurl set some flag/option on the socket under connect stage, and slow the read. But I also find it unreasonable.
I don't know where the problem is neither. I wanna try the raw socket and do not use libcurl.

 
----- Original Message -----From: Daniel Stenberg <daniel_at_haxx.se>
To: the curl tool <curl-users_at_cool.haxx.se>

On Fri, 13 Jan 2012, curl wrote:

> I also tried to get socket using curl_easy_getinfo(handle,
> CURLINFO_LASTSOCKET, &sock); and then read using system call "read" from
> socket, and the speed is keep the same as before, 12Mbyte. So I think the
> problem maybe under the connect stage.

I don't understand. Are you suggesting the connect handshake somehow damages
the ability to do fast transfers?

If you check the code, curl_easy_recv() is a very thin wrapper around recv()
when you use plain text protocols.

--

  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-01-13