Re: [PROF RFC 1/2] profiling of libcurl by curl-loader, steady state
Date: Tue, 17 Apr 2007 22:47:12 +0200 (CEST)
On Tue, 17 Apr 2007, Robert Iakobashvili wrote:
(Replying only to a part of the previous message - for now)
> Sorry, for the poor explanation. libcurl library verbose mode was always on
> during these profiling experiments.
Ah, ok. That explains the extensive use of *printf(). In my view, it would be
more interesting to do the profiling without verbose mode.
> It was curl-loader's verbose mode was off which has another meaning, namely:
> - don't print to the logfile file any messages besides having CURLINFO_ERROR
> level (our patch to split CURLINFO_TEXT to errors and indeed info text).
I don't see the need for that patch/CURLINFO_ERROR. It simply makes the output
that would otherwise be stored in the CURLOPT_ERRORBUFFER get sent to the
debug callback instead and there you filter out only that. I would rather
recommend you using CURLOPT_ERRORBUFFER instead, as it would then also reduce
the amount of *printf()s etc within libcurl.
-- Commercial curl and libcurl Technical Support: http://haxx.se/curl.htmlReceived on 2007-04-17