RE: Not ramping up IP addresses correctly when TCP connections remain open

[Bellorado, A. <abe...@ve...>]

To force the TCP connections not to be reused, I tried using the -r option with version 0.47 during the curl-loader execution command and this did not cause curl-loader to close the TCP connections after finishing the transaction as I expected.  Then, I tried including the 'FRESH_CONNECT=1' option for each URL, and curl-loader did properly close the connection for each transaction.  With the connections not being re-used, the client IP addresses were ramped up correctly.

With this said, is there a way to use curl-loader to ramp up clients using properly incrementing IP addresses without closing the TCP connection after a transaction is complete?  Thanks in advance for the help and prompt response.


Aron

________________________________
From: Robert Iakobashvili [mailto:cor...@gm...]
Sent: Tuesday, February 24, 2009 3:20 PM
To: curl-loader-devel
Subject: Re: Not ramping up IP addresses correctly when TCP connections remain open

Hi Aron,
On Tue, Feb 24, 2009 at 9:56 PM, Bellorado, Aron <abe...@ve...<mailto:abe...@ve...>> wrote:
I am using curl-loader 0.47 against an Apache web server running HTTP 1.1.  With the Apache web server "KeepAlive" config parameter set to OFF, curl-loader properly ramp ups the number of clients based on the specific batch file parameters as expected with the Apache web server closing every connection after each transaction is made.  The attached capture file "withKeepAliveOff.cap" shows this proper behavior using the curl-loader batch file shown below.

When Apache was configured with "KeepAlive" set to ON, the web server does not close the TCP connection after a transaction is complete leaving the connection open for the client for subsequent transactions.  When curl-loader was run an Apache web server with Keep Alive set to ON, curl-loader does not ramp up the clients correctly not incrementing IP address appropriately during the ramp up time.  Curl-loader appears to be reusing existing client IP addresses (possibly because the connections are still open) instead of using incremented IP addresses, although the curl-loader log files show the IP addresses are being incremented properly.  The attached capture file "withKeepAliveOn.cap" shows this incorrect behavior using the same curl-loader batch file shown below.  Any help would be greatly appreciated.


This behavior is inherited from libcurl.
Try to configure the connections not to be re-used (there is a tag for that),
but it is not necessarily will be helpful to keep KA connections with apache.



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