curl-loader-devel — curl-loader usage and development issues

Re: Curl-Loader for XML based Requests over https.

[Robert I. <cor...@gm...>]

Hi Sridhar

On Tue, Oct 13, 2009 at 1:28 PM, Sridhar Kotha <sri...@ya...>wrote:

>  Hi,
>
> Curl Loader tool is not working for XML requests over HTTPS.
>
I seriously doubt this statement.
The truth is probably, that it doesn't work for your network layout.

So what are the errors, that you see in the logfile?

The errors that you sent the last time were connected to that the network
addresses, that you used were most probably non-routable.


>  --
> Truly,
> Robert Iakobashvili, Ph.D.
> ......................................................................
> www.ghotit.com
> Assistive technology that understands you
> ......................................................................
>

RE: Curl-Loader for XML based Requests over https.

[Sridhar K. <sri...@ya...>]

Hi,
Curl Loader tool is not working for XML requests over HTTPS.
Command used is:
sudo ./curl-loader -f conf-examples/prodorder.conf -u -v

My Conf file contents are:
-------------------------------------

-sh-3.00$ cat conf-examples/prodorder.conf
########### GENERAL SECTION ################################

BATCH_NAME= httpsXMLReq
CLIENTS_NUM_MAX= 1
INTERFACE   = eth0
NETMASK= 24
IP_ADDR_MIN= 10.66.72.242
IP_ADDR_MAX= 10.66.72.242
CYCLES_NUM= 1
URLS_NUM= 1

########### URL SECTION ####################################

URL=https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
URL_SHORT_NAME="post-xml"
REQUEST_TYPE=POST
MULTIPART_FORM_DATA="file=@/home/sridhark/performance/curl-loader-0.50/conf-examples/ysbsqa-skotha-mudperf1.xml"
TIMER_URL_COMPLETION = 500
TIMER_AFTER_URL_SLEEP = 0

XML Request is:
-sh-3.00$ cat conf-examples/ysbsqa-skotha-mudperf1.xml
<?xml version="1.0" encoding="utf-8"?>
<ystorewsRequest>
 <StoreID>ysbsqa-skotha-mudperf1</StoreID>
 <SecurityHeader>
                <PartnerStoreContractToken>1.0_AxAuYuls_wG_A8pzSPzrbNKXYqGKP6Kmv8tUk_gbeVOIBaYf6neyBds1SzBFee0gAvhdslrddUqOLtFmVez7DEarQyNvn4jdPfzTyjJ5J4qtxQ9jzkZVT3YxwsPEzjV1jliF3wrY6Am9</PartnerStoreContractToken>
 </SecurityHeader>
 <Version>1.0</Version>
 <Verb> get </Verb>
 <ResourceList>
  <OrderListQuery>
   <Filter>
    <Include> all </Include>
   </Filter>
   <QueryParams>
    <OrderID>490</OrderID>
   </QueryParams>
  </OrderListQuery>
 </ResourceList>
</ystorewsRequest>

Any help on this is highly appreciated.
Best regards,
Sridhar K



________________________________
From: Sridhar Kotha
Sent: Monday, October 05, 2009 9:28 PM
To: 'cur...@li...'
Subject: Curl-Loader for XML based Requests over https.

Hi,
I am trying to use curl-loader tool for sending xml requests over https.
Manually I can execute the same using curl but with the tool, it is not working.
My configuration file is:


URL=https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
URL_SHORT_NAME="post-xml"
REQUEST_TYPE=POST
MULTIPART_FORM_DATA="file=@/home/sridhark/performance/curl-loader-0.50/conf-examples/ysbsqa-skotha-mudperf1.xml"
TIMER_URL_COMPLETION = 500
TIMER_AFTER_URL_SLEEP = 0

Command used:  sudo ./curl-loader -f conf-examples/prodorder.conf -v

-sh-3.00$ cat https.log
# 627973937 Mon Oct  5 21:30:24 2009
# msec_offset cycle_no url_no client_no (ip) indic info
1 0 0 1 == About to connect() to ysbsqa-skotha-mudperf1.order.store.yahooapis.com port 443 (#0) eff-url: url https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
542 0 0 1  !! ERUT url completion timeout: url: https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
542 0 0 1 == Closing connection #0 eff-url: url https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order

The xml to be posted is in the conf-examples.  Kindly tell me how to send the xml based requests.  Also let me know if sending XML requests over HTTPS is supported or not.
Many Thanks and Best Regards,
Sridhar K

curl-loader is not for windows

[Robert I. <cor...@gm...>]

Hi Hari,

Please, read the FAQs
http://curl-loader.sourceforge.net/doc/faq.html

You can use any operating system of your choice,
providing that the OS is linux.

:-)

Take care,
Sincerely,
Robert

Initial Comment:
Hi,
I am unable to create a setup file in my XP system.
Can any body provide me a pre build exe.
can provide the files at sign2hari(at)gmail(dot)com

with regards
hari

-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

Re: bug report

[Gary F. <ga...@iF...>]

Hello Robert,

I'm on the road for two more weeks, with no access to source.
I will take a look as soon as I get back.

Gary


On Oct 7, 2009, at 10:09 PM, Robert Iakobashvili wrote:

Hi Val,

On Thu, Oct 8, 2009 at 5:15 AM, Val Shkolnikov <va...@nv...> wrote:
Hi Robert,
    I found a bug in parse_conf.c but, regretfully, do not have a fix  
yet.  It has to do with the option RESPONSE_STATUS_ERRORS failing in  
the presence of another option URL_TEMPLATE.  It happens very  
infrequently, but I came up with a script and a bunch of support files  
that demonstrate the problem.  The script runs until failure and it  
repeats from 10 to 100 times before a failure.  There is a small  
readme file that tells you what to do.  Maybe someone will have some  
bright ideas how to fix this.  The script runs gdb which puts a single  
breakpoint into parse_conf.c to prevent it to going further if the  
failure did not occur.  This line number is for SVN revision 570.

Regards,
/Val


Val, thanks for your reported! I'll try to learn this.

Gary,
if you have a time-slot to look at that, it would be very much  
appreciated!
Thanks!

Re: bug report

[Robert I. <cor...@gm...>]

Hi Val,

On Thu, Oct 8, 2009 at 5:15 AM, Val Shkolnikov <va...@nv...> wrote:

> Hi Robert,
>    I found a bug in parse_conf.c but, regretfully, do not have a fix yet.
> It has to do with the option RESPONSE_STATUS_ERRORS failing in the presence
> of another option URL_TEMPLATE.  It happens very infrequently, but I came up
> with a script and a bunch of support files that demonstrate the problem.
> The script runs until failure and it repeats from 10 to 100 times before a
> failure.  There is a small readme file that tells you what to do.  Maybe
> someone will have some bright ideas how to fix this.  The script runs gdb
> which puts a single breakpoint into parse_conf.c to prevent it to going
> further if the failure did not occur.  This line number is for SVN revision
> 570.
>
> Regards,
> /Val
>


Val, thanks for your reported! I'll try to learn this.

Gary,
if you have a time-slot to look at that, it would be very much appreciated!
Thanks!

-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

bug report

[Val S. <va...@nv...>]

‹

Re: Curl-Loader for XML based Requests over https.

[Robert I. <cor...@gm...>]

Hi Sridhar

On Mon, Oct 5, 2009 at 5:58 PM, Sridhar Kotha <sri...@ya...>wrote:

>  Hi,
>
> I am trying to use curl-loader tool for sending xml requests over https.
>
Please, always fill the PRF form.


> URL=https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
>
> URL_SHORT_NAME="post-xml"
>
> REQUEST_TYPE=POST
>
>
> MULTIPART_FORM_DATA="file=@/home/sridhark/performance/curl-loader-0.50/conf-examples/ysbsqa-skotha-mudperf1.xml"
>
> TIMER_URL_COMPLETION = 500
>
> TIMER_AFTER_URL_SLEEP = 0
>
>
>
> Command used:  sudo ./curl-loader -f conf-examples/prodorder.conf –v
>
>
>
> -sh-3.00$ cat https.log
>
> # 627973937 Mon Oct  5 21:30:24 2009
>
> # msec_offset cycle_no url_no client_no (ip) indic info
>
> 1 0 0 1 == About to connect() to
> ysbsqa-skotha-mudperf1.order.store.yahooapis.com port 443 (#0) eff-url:
> url https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
>
> 542 0 0 1  !! ERUT url completion timeout: url:
> https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
>
> 542 0 0 1 == Closing connection #0 eff-url: url
> https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
>
>
>
Something is wrong with your network/addresses configuration or DNS.

You have not provided your full configuration file.

The address/es with netmask should be routable to the URL, that you are
testing.
Please, consult you network admin.

As a tip, try to use in curl the same address as the address of your
computer.


> The xml to be posted is in the conf-examples.  Kindly tell me how to send
> the xml based requests.  Also let me know if sending XML requests over HTTPS
> is supported or not.
>

Nothing to do with XML body here.
There are HOWTOS for sending XML files. Please, read them.


> Many Thanks and Best Regards,
>
> Sridhar K
>

-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

Curl-Loader for XML based Requests over https.

[Sridhar K. <sri...@ya...>]

Hi,
I am trying to use curl-loader tool for sending xml requests over https.
Manually I can execute the same using curl but with the tool, it is not working.
My configuration file is:


URL=https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
URL_SHORT_NAME="post-xml"
REQUEST_TYPE=POST
MULTIPART_FORM_DATA="file=@/home/sridhark/performance/curl-loader-0.50/conf-examples/ysbsqa-skotha-mudperf1.xml"
TIMER_URL_COMPLETION = 500
TIMER_AFTER_URL_SLEEP = 0

Command used:  sudo ./curl-loader -f conf-examples/prodorder.conf -v

-sh-3.00$ cat https.log
# 627973937 Mon Oct  5 21:30:24 2009
# msec_offset cycle_no url_no client_no (ip) indic info
1 0 0 1 == About to connect() to ysbsqa-skotha-mudperf1.order.store.yahooapis.com port 443 (#0) eff-url: url https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
542 0 0 1  !! ERUT url completion timeout: url: https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order
542 0 0 1 == Closing connection #0 eff-url: url https://ysbsqa-skotha-mudperf1.order.store.yahooapis.com/V1/order

The xml to be posted is in the conf-examples.  Kindly tell me how to send the xml based requests.  Also let me know if sending XML requests over HTTPS is supported or not.
Many Thanks and Best Regards,
Sridhar K

Re: curl-loader version 0.50 released

[Val S. <va...@nv...>]

Robert,
    perhaps you should update the FAQ's tag section to explain the new tags.
/Val


>
>From: Robert Iakobashvili <cor...@gm...>
>To: curl-loader-devel <cur...@li...>
>Sent: Monday, September 21, 2009 10:18:13 AM
>Subject: curl-loader version 0.50 released
>
>>Hi folks,
>
>We have a new release. Many thanks to
>the great people that have contributed to this release.
>
>
>
>version 0.50, unstable, September 21, svn 570
>
>* Advanced to curl-7.19.6, which is closing dead connections faster
>>  and contains other important fixes.
>
>By Val Shkolnikov <va...@nv...>
>* Added a fixed request rate feature.
>  It is a bit risky feature, but "Navigare necesse est ..."
>>* Fixed a bug for fixed-rate, where curl-loader would not stop on run time 
>  expiration or url completion
>
>By Val Shkolnikov <va...@nv...>
>* Directed operational statistics into a file with the extension .ops
>>* Added DUMP_OPSTATS and RUN_TIME options.
>* Added time stamp to the .log file, streamlined logging using macros.
>* Added a second -v option for varied level of logging detail.
>
>* Renamed function getline to get_line since folks from RedHat are 
>>   polluting the namespace. Thanks to jari pietila <jar...@ho...>
>   for reporting that.
>
>* Fixed x86_64 arch revealed stack smashing bug in parse_conf.c Thanks to nobody/anonymous.
>
>-- 
>Truly,
>Robert Iakobashvili, Ph.D.
>......................................................................
>www.ghotit.com
>Assistive technology that understands you
>>......................................................................
>

curl-loader version 0.50 released

[Robert I. <cor...@gm...>]

Hi folks,

We have a new release. Many thanks to
the great people that have contributed to this release.



version 0.50, unstable, September 21, svn 570

* Advanced to curl-7.19.6, which is closing dead connections faster
  and contains other important fixes.

By Val Shkolnikov <va...@nv...>
* Added a fixed request rate feature.
  It is a bit risky feature, but "Navigare necesse est ..."
* Fixed a bug for fixed-rate, where curl-loader would not stop on run time
  expiration or url completion

By Val Shkolnikov <va...@nv...>
* Directed operational statistics into a file with the extension .ops
* Added DUMP_OPSTATS and RUN_TIME options.
* Added time stamp to the .log file, streamlined logging using macros.
* Added a second -v option for varied level of logging detail.

* Renamed function getline to get_line since folks from RedHat are
   polluting the namespace. Thanks to jari pietila <jar...@ho...>
   for reporting that.

* Fixed x86_64 arch revealed stack smashing bug in parse_conf.c Thanks to
nobody/anonymous.

-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

Re: bug fix

[Robert I. <cor...@gm...>]

H Val,

On Thu, Sep 10, 2009 at 11:25 PM, Val Shkolnikov <va...@nv...> wrote:

>  Hi Robert,
>    Attached is a patch against source-forge rev. 567 for the following
> bug:  curl-loader would not stop on run time expiration or url completion if
> the fixed request rate is in effect.  To install the patch please run in the
> curl-loader directory:
>
> patch <curl-loader-patch.567+vs4
>
> Regards,
> Val
>
>
Applied. Thanks!

-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

bug fix

[Val S. <va...@nv...>]

diff -rupN curl-loader.567/trunk/curl-loader/batch.h curl-loader.567+vs4/batch.h
--- curl-loader.567/trunk/curl-loader/batch.h	2009-09-10 12:33:14.000000000 -0700
+++ curl-loader.567+vs4/batch.h	2009-09-07 21:33:26.000000000 -0700
@@ -220,6 +220,9 @@ typedef struct batch_context
   /* List of clients free to send fixed rate requests */
   int* free_clients;
 
+  /* Indicates that request scheduling is over */
+  int requests_completed;
+
   /* Request rate timer invocation sequence number within a second */
   int req_rate_timer_invocation;
 
diff -rupN curl-loader.567/trunk/curl-loader/loader_fsm.c curl-loader.567+vs4/loader_fsm.c
--- curl-loader.567/trunk/curl-loader/loader_fsm.c	2009-09-10 12:33:14.000000000 -0700
+++ curl-loader.567+vs4/loader_fsm.c	2009-09-08 17:30:13.000000000 -0700
@@ -363,7 +363,10 @@ int load_next_step (client_context* cctx
   */
   int recoverable_error_state = cctx->client_state;
   if (bctx->run_time && (now_time - bctx->start_time >= bctx->run_time))
+    {
       rval_load = CSTATE_FINISHED_OK;
+      bctx->requests_completed = 1;
+    }
   else
   /* 
      Initialize virtual client's CURL handle for the next step of loading by calling
@@ -1028,6 +1031,8 @@ static int handle_req_rate_timer (timer_
  ****************************************************************************************/
 int pending_active_and_waiting_clients_num (batch_context* bctx)
 {
+  if (bctx->req_rate && (bctx->cycling_completed || bctx->requests_completed))
+    return 0;
   int total = bctx->waiting_queue ? 
     (bctx->active_clients_count + bctx->sleeping_clients_count) :
     bctx->active_clients_count;

Re: support for client certificate auth

[Robert I. <cor...@gm...>]

Hi Walter

On Tue, Sep 8, 2009 at 9:51 PM, Walter Brown <wal...@ya...> wrote:

>    Hello,
>
> I didn't see anything in the docs about curl-loader supporting client cert
> auth, can this be done or is it planned?
>
> If it is supported is there a guide to assist with setup?   I am able to do
> the client side cert auth when using regular curl so perhaps there is a way
> to manipulate curl-loader also?
>
> Thanks,
> Walter
>
>
Since it is supported by licurl, this is not a big deal to develop patches
for that in curl-loader.
If you know C-lang, I can guide you.


-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

support for client certificate auth

[Walter B. <wal...@ya...>]

Hello,

I didn't see anything in the docs about curl-loader supporting client cert auth, can this be done or is it planned?

If it is supported is there a guide to assist with setup?   I am able to do the client side cert auth when using regular curl so perhaps there is a way to manipulate curl-loader also?

Thanks,
Walter


      

Re: Posting to redirected HTTP request

[Robert I. <cor...@gm...>]

Hi Rowshan,

On Sat, Sep 5, 2009 at 1:38 AM, Rowshan Dowlatabadi <dro...@ya...>wrote:

> I am trying to send the user name and password to a redirected page.
> Basically, when I open www.example.com, the proxy server redirects the
> browser to another page (http://ProxyServerIP:Port/cgi-bin/auth?) which
> has a user name, password files and an image button for submitting the
> credential. After providing the correct user name and password, the browser
> shows the original page www.example.com.
>
> Is it possible to accomplish this using curl-loader? If so, how?
>
>
> Sure, This is the most basic scenario cared by the tool.

The redirections are cared automatically.

Look at the example, e.g. curl-loader/conf-examples/bax.conf
Here the first URL redirects to the second URL, which is empty as it is
resulting
from the redirection process. The second URL is a POST form and parameters
are passed there.

Reading of FAQs could be also productive, which are located in README or
here:
http://curl-loader.sourceforge.net/doc/faq.html#conf-file-details

Take care!



> --
> Truly,
> Robert Iakobashvili, Ph.D.
> ......................................................................
> www.ghotit.com
> Assistive technology that understands you
> ......................................................................
>

Posting to redirected HTTP request

[Rowshan D. <dro...@ya...>]

I am trying to send the user name and password to a redirected page. Basically, when I open www.example.com, the proxy server redirects the browser to another page (http://ProxyServerIP:Port/cgi-bin/auth?) which has a user name, password files and an image button for submitting the credential. After providing the correct user name and password, the browser shows the original page www.example.com.

Is it possible to accomplish this using curl-loader? If so, how?



      

Re: How do I set send and recv buffers using curl-loader

[Paddy G. <pad...@gm...>]

Hi Robert,


On Thu, Sep 3, 2009 at 12:59 AM, Robert Iakobashvili <cor...@gm...>wrote:

>
> If you would like to make patches for libcurl and curl-loader to make this
> configurable,
> I can guide you.
>
> Yes. I would like to make a patch where this is configurable.
Thank you. I would need your help in getting this right..

-paddy

Re: How do I set send and recv buffers using curl-loader

[Robert I. <cor...@gm...>]

Hi Paddy,

On Fri, Aug 28, 2009 at 8:39 PM, Paddy Ganti <pad...@gm...> wrote:

> First off, thank you for the prompt response and supporting this wonderful
> tool.
>
>  On Wed, Aug 26, 2009 at 11:05 PM, Robert Iakobashvili <
> cor...@gm...> wrote:
>
>> I have no idea about httpperf, but may be other users have some
>> experience.
>
>
> http://httperf.comlore.com/Home gives you some idea of recent advances to
> the original paper (
> http://www.hpl.hp.com/research/linux/httperf/wisp98/httperf.pdf)
>
>>
>>
>> Neither we nor libcurl (the HTTP stack) are playing with socket default
>> buffers at linux.
>> There is no point in playing with them for a web-client.
>
>
> It is critical for WAN latencies. If the buffers are too small, like they
> are when default values are used, the TCP congestion window will never fully
> open up (particularly on long fat networks)
>

If you would like to make patches for libcurl and curl-loader to make this
configurable,
I can guide you.


-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

Re: How do I set send and recv buffers using curl-loader

[Paddy G. <pad...@gm...>]

First off, thank you for the prompt response and supporting this wonderful
tool.

On Wed, Aug 26, 2009 at 11:05 PM, Robert Iakobashvili
<cor...@gm...>wrote:

> I have no idea about httpperf, but may be other users have some experience.


http://httperf.comlore.com/Home gives you some idea of recent advances to
the original paper (
http://www.hpl.hp.com/research/linux/httperf/wisp98/httperf.pdf)

>
>
> Neither we nor libcurl (the HTTP stack) are playing with socket default
> buffers at linux.
> There is no point in playing with them for a web-client.


It is critical for WAN latencies. If the buffers are too small, like they
are when default values are used, the TCP congestion window will never fully
open up (particularly on long fat networks)
http://www.cisco.com/web/about/ac123/ac147/ac174/ac196/about_cisco_ipj_archive_article09186a00800c8417.htmlhas
more information (TCP Volume Transfer section near Figure 7))



>
> You can change the client window size by playing with this parameter in
> Makefile,
> whereas I have doubts, whether it has a serious performance impact, but may
> be with
> some rare web-servers.


I did a small experiment in my lab wherein I get a 100K file with 16K buffer
as well as 64K buffer over a 330ms network.
With 16K the response time was 17.161 s whereas just tweaking the buffer
size gives you 7.589 s

Thank you again.

-Paddy

ps: The lab output for my 100K file so you can simulate the same

16K Buffer
-------------------

httperf --timeout=5 --client=0/1 --server=web.lab --port=80 --uri=/100K
--rate=60 --send-buffer=4096 --recv-buffer=16384 --num-conns=1
--num-calls=10
Maximum connect burst length: 0

Total: connections 1 requests 10 replies 10 test-duration 17.161 s

Connection rate: 0.1 conn/s (17160.7 ms/conn, <=1 concurrent connections)
Connection length [replies/conn]: 10.000

num avg stddev min 10% 25% 50% 75% 90% 95% 99% max
Connection life [ms] 1 17160.7 0.0 17160.7 17160 17160 17160 17160 17160
17160 17160 17160.7
Handshake time [ms] 1 330.1 0.0 330.1 330 330 330 330 330 330 330 330.1
Response time [ms] 10 329.9 0.3 329.7 330 330 330 330 330 330 330 330.8
Transfer time [ms] 10 1353.1 104.4 1320.1 1320 1320 1320 1320 1650 1650 1650
1650.3

Request rate: 0.6 req/s (1716.1 ms/req)
Request size [B]: 62.0

Reply rate [replies/s]: min 0.0 avg 0.5 max 0.6 stddev 0.1 (3 samples)
Reply size [B]: header 234.0 content 106404.0 footer 0.0 (total 106638.0)
Reply status: 1xx=0 2xx=10 3xx=0 4xx=0 5xx=0

CPU time [s]: user 4.88 system 12.27 (user 28.5% system 71.5% total 100.0%)
Net I/O: 60.7 KB/s (0.5*10^6 bps)

Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0
Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0


64K Buffer
-------------
 httperf --timeout=5 --client=0/1 --server=web.lab --port=80 --uri=/100K
--rate=60 --send-buffer=4096 --recv-buffer=65535 --num-conns=1
--num-calls=10
httperf --timeout=5 --client=0/1 --server=web.lab --port=80 --uri=/100K
--rate=60 --send-buffer=4096 --recv-buffer=65535 --num-conns=1
--num-calls=10
Maximum connect burst length: 0

Total: connections 1 requests 10 replies 10 test-duration 7.589 s

Connection rate: 0.1 conn/s (7589.1 ms/conn, <=1 concurrent connections)
Connection length [replies/conn]: 10.000

num avg stddev min 10% 25% 50% 75% 90% 95% 99% max
Connection life [ms] 1 7589.1 0.0 7589.1 7590 7590 7590 7590 7590 7590 7590
7589.1
Handshake time [ms] 1 329.2 0.0 329.2 330 330 330 330 330 330 330 329.2
Response time [ms] 10 329.9 0.1 329.6 330 330 330 330 330 330 330 330.0
Transfer time [ms] 10 396.1 208.8 330.0 330 330 330 330 990 990 990 990.4

Request rate: 1.3 req/s (758.9 ms/req)
Request size [B]: 62.0

Reply rate [replies/s]: min 0.0 avg 1.2 max 1.2 stddev 0.0 (1 samples)
Reply size [B]: header 234.0 content 106404.0 footer 0.0 (total 106638.0)
Reply status: 1xx=0 2xx=10 3xx=0 4xx=0 5xx=0

CPU time [s]: user 1.35 system 6.24 (user 17.7% system 82.2% total 100.0%)
Net I/O: 137.3 KB/s (1.1*10^6 bps)

Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0
Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0

>
>
> Take care!
>
>
> --
> Truly,
> Robert Iakobashvili, Ph.D.
> ......................................................................
> www.ghotit.com
> Assistive technology that understands you
> ......................................................................
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> curl-loader-devel mailing list
> cur...@li...
> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel
>
>

Re: How do I set send and recv buffers using curl-loader

[Robert I. <cor...@gm...>]

Hi Paddy

On Wed, Aug 26, 2009 at 8:55 PM, Paddy Ganti <pad...@gm...> wrote:

> I am new to curl-loader coming from the world of httperf.I am assuming that
> the default receive buffer is set via CURL_MAX_WRITE_SIZE to 16384 .
>
> In httperf, I can set the socket receive buffer size([--recv-buffer N]
> [--send-buffer N) but couldnt glean such information from the README/FAQ of
> curl-loader
>
> Any idea on how to go about setting these sizes?
>
> Thanks
> -Paddy
>

I have no idea about httpperf, but may be other users have some experience.

Neither we nor libcurl (the HTTP stack) are playing with socket default
buffers at linux.
There is no point in playing with them for a web-client.

CURL_MAX_WRITE_SIZE impacts the advertised client window in TCP.
When it is 16K - it will be 16K, when 32K - 32K.

You can change the client window size by playing with this parameter in
Makefile,
whereas I have doubts, whether it has a serious performance impact, but may
be with
some rare web-servers.

Take care!


-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

How do I set send and recv buffers using curl-loader

[Paddy G. <pad...@gm...>]

I am new to curl-loader coming from the world of httperf.I am assuming that
the default receive buffer is set via CURL_MAX_WRITE_SIZE to 16384 .

In httperf, I can set the socket receive buffer size([--recv-buffer N]
[--send-buffer N) but couldnt glean such information from the README/FAQ of
curl-loader

Any idea on how to go about setting these sizes?

Thanks
-Paddy

Re: !! ERROR: Protocol https not supported or disabled in libcurl

[Robert I. <cor...@gm...>]

Hi,

On Tue, Aug 25, 2009 at 9:12 AM, chaitanya varma <cva...@gm...> wrote:

> Thanks for the reply, I had the openssl installed in my  box. accessing the
> https sites is working just fine with wget,ab and curl. but, I am facing
> issues making it work with curl-loader.
> Also, as a note, I had no issues while installing tool.
>
> I am planning to make it work with this particular tool as I wanted to
> generate 1000s of https  connections.
>
> Thanks,
> Penmetsa
>
>
Y might be missing the point.
Please, make sure, that you have headers of openssl (the development
package),
read the FAQs

The building process of libcurl creates file
curl-loader/build/curl/config.log

Y might wish to read the file and understand the reason of https being
disabled
(no openssl headers, binaries, etc).

Take care.

-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

Re: !! ERROR: Protocol https not supported or disabled in libcurl

[chaitanya v. <cva...@gm...>]

Thanks for the reply, I had the openssl installed in my  box. accessing the
https sites is working just fine with wget,ab and curl. but, I am facing
issues making it work with curl-loader.
Also, as a note, I had no issues while installing tool.

I am planning to make it work with this particular tool as I wanted to
generate 1000s of https  connections.

Thanks,
Penmetsa




On Mon, Aug 24, 2009 at 10:41 PM, Robert Iakobashvili
<cor...@gm...>wrote:

> Hi Penmentsa,
>
> On Tue, Aug 25, 2009 at 3:28 AM, chaitanya varma <cva...@gm...>wrote:
>
>> I have installed the curl-loader-0.49 on cent OS 5.0. For http traffic,
>> the tool is working great. But, when I tried the https access, the
>> connections are failing and the https.logs says " !! ERROR: Protocol https
>> not supported or disabled in libcurl".
>>
>> Can you guide me what exactly need to be done to fix the issue....
>>
>> Thanks,
>> Penmetsa
>>
>
> Since we are building libcurl with support for SSL/HTTPS,
> it could be, if it does not see the openssl headers, or there are no
> openssl
> binaries at your linux, which is less probable.
>
> Please, read the section:
>
> http://curl-loader.sourceforge.net/doc/faq.html#building
>
>
>
> --
> Truly,
> Robert Iakobashvili, Ph.D.
> ......................................................................
> www.ghotit.com
> Assistive technology that understands you
> ......................................................................
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> curl-loader-devel mailing list
> cur...@li...
> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel
>
>

Re: !! ERROR: Protocol https not supported or disabled in libcurl

[Robert I. <cor...@gm...>]

Hi Penmentsa,

On Tue, Aug 25, 2009 at 3:28 AM, chaitanya varma <cva...@gm...> wrote:

> I have installed the curl-loader-0.49 on cent OS 5.0. For http traffic, the
> tool is working great. But, when I tried the https access, the connections
> are failing and the https.logs says " !! ERROR: Protocol https not supported
> or disabled in libcurl".
>
> Can you guide me what exactly need to be done to fix the issue....
>
> Thanks,
> Penmetsa
>

Since we are building libcurl with support for SSL/HTTPS,
it could be, if it does not see the openssl headers, or there are no openssl
binaries at your linux, which is less probable.

Please, read the section:

http://curl-loader.sourceforge.net/doc/faq.html#building



-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................

!! ERROR: Protocol https not supported or disabled in libcurl

[chaitanya v. <cva...@gm...>]

I have installed the curl-loader-0.49 on cent OS 5.0. For http traffic, the
tool is working great. But, when I tried the https access, the connections
are failing and the https.logs says " !! ERROR: Protocol https not supported
or disabled in libcurl".

Can you guide me what exactly need to be done to fix the issue....

Thanks,
Penmetsa