On 4/18/07, Robert Iakobashvili <coroberti_at_gmail.com> wrote:
> The affect of incrementing number of loading clients
> by 20 clients each second. Starting stage.

libcurl makes a great job and performs well in steady state of http
loads. Some areas to improve, like too much gettimeofday (),
do not change this in general good picture.

The motivation behind these earlier posted profiling data at the
ramp stage was to draw attention to the performance issues
during connection establishment.

When we attempted to add 100 and more clients each second to load,
it has completely burned out the CPU. The experiments posted were
done with only 20 clients added each second to enable reliable profiling with
oprofile. Both gprof and oprofile data show, the CreateConnection () takes
a lot of CPU.

Other CPU consumers were rather expected with exception may be of
hash functions (see also *.lprof files), which are normally do not top any
CPU profiling.

Hopefully, curl gurus will have some time to look at the data and to share their
analyzes with areas for improvement.

Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...................................................................
Navigare necesse est, vivere non est necesse
...................................................................
http://curl-loader.sourceforge.net
An open-source HTTP/S, FTP/S traffic
generating, and web testing tool.
Received on 2007-04-24