Re: FRESH_CONNECT=1 and TIMER_AFTER_URL_SLEEP =5000

[BuraphaLinux S. <bur...@gm...>]

Hello,

    In testing I did not see any difference.  In the logs I get blocks
like this when curl-loader is cycling too fast (sorry gmail wraps
badly):

: eff-url: ftp://anonymous:joe%040@10.16.68.213/apache/httpd/httpd-2.0.59.tar.bz2,
url:
121 20 (10.16.68.197)  <= Recv header: eff-url:
ftp://anonymous:joe%040@10.16.68.213/apache/httpd/httpd-2.0.59.tar.bz2,
url:
121 20 (10.16.68.197) :<= WARNING: parsing error: wrong response code (FTP?) 0 .
121 20 (10.16.68.197)  !! ERROR: This doesn't seem like a nice
ftp-server response
: eff-url: ftp://anonymous:joe%040@10.16.68.213/apache/httpd/httpd-2.0.59.tar.bz2,
url:
121 20 (10.16.68.197)  :== Info: Expire cleared
: eff-url: ftp://anonymous:joe%040@10.16.68.213/apache/httpd/httpd-2.0.59.tar.bz2,
url:
121 20 (10.16.68.197)  :== Info: Closing connection #117

I worry that 'parsing error' means it doesn't do the delay, but I
don't really know.
The server side of this will say this in the vsftpd log file:

Sun Aug  5 18:17:58 2007 [pid 10839] CONNECT: Client "10.16.68.197",
"Connection refused: too many sessions."

Using ss -tan (or netstat) I can verify there are too many connections
on the server.
The vsftpd server has been set for 100 clients with these entries in
vsftpd.conf:

#
# Maximum number of simultaneous clients
#
max_clients=100
#
# Maximum number of connections from 1 ip
#
max_per_ip=100

(and I painfully tested by hand that this limit works as expected)

My configuration is ftp.small for curl-loader and is this:

########### GENERAL SECTION ################################

BATCH_NAME= ftpsmall
CLIENTS_NUM_MAX=50 # Same as CLIENTS_NUM
CLIENTS_NUM_START=5
CLIENTS_RAMPUP_INC=5
INTERFACE=eth0
NETMASK=32
IP_ADDR_MIN=10.16.68.197
IP_ADDR_MAX=10.16.68.197
CYCLES_NUM=-1
URLS_NUM=1

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

URL=ftp://anonymous:joe%040@10.16.68.213/apache/httpd/httpd-2.0.59.tar.bz2
FRESH_CONNECT=1
URL_SHORT_NAME="small"
TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced
by cancelling url fetch on timeout
TIMER_AFTER_URL_SLEEP =5000
TIMER_TCP_CONN_SETUP=50

and was invoked with this script (as root user):

#! /sbin/bash
rm -fr ftpsmall.*
ulimit -d unlimited
ulimit -f unlimited
ulimit -m unlimited
ulimit -n 19999
ulimit -t unlimited
ulimit -u unlimited
ulimit -v unlimited
ulimit -x unlimited
echo 1 > /proc/sys/net/ipv4/tcp_tw_recycle
echo 1 > /proc/sys/net/ipv4/tcp_tw_reuse
echo 1 > /proc/sys/net/ipv4/tcp_ecn
echo 1 > /proc/sys/net/ipv4/tcp_window_scaling
curl-loader -f ftp.small -v -u -w

With the limit set to 50 on the client and the delays, I expect having
the server set to 100 should be enough to let this script run without
errors, but it never does.  What am I doing wrong?  I can provide more
data, but I need to know what data will help you.  Please let me know.
 I didn't attach the entire curl-loader log since even for a few
minute run it was 38MB.

JGH


On 8/5/07, Robert Iakobashvili <cor...@gm...> wrote:
> On 8/2/07, BuraphaLinux Server <bur...@gm...> wrote:
> >
> > On 8/2/07, Robert Iakobashvili <cor...@gm...> wrote:
> > >
> > > My understanding here is that, when FRESH_CONNECT is set,
> > > we need:
> > > 1) to close the connection;
> > > 2) only after the connection is closed to sleep for
> > TIMER_AFTER_URL_SLEEP;
> >
> >     Yes, you understand the problem and what the solution is.  I look
> > forward to testing your fix.  Thanks!
> >
> > JGH
> >
>
> Please, try the latest svn version.
> Unfortunately, I am short in time to test it properly and only
> run a small test.
> Please, test, if it works for you.
>
> --
> Sincerely,
> Robert Iakobashvili,
> coroberti %x40 gmail %x2e com
> ...........................................................
> http://curl-loader.sourceforge.net
> A web testing and traffic generation tool.
>