Re: TIMER_AFTER_URL_SLEEP question

[Pranav D. <pra...@gm...>]

On Feb 18, 2008 10:03 PM, Robert Iakobashvili <cor...@gm...> wrote:
> Pranav,
>
>
> On Feb 19, 2008 5:12 AM, Pranav Desai <pra...@gm...> wrote:
> >
> >
> > Will definitely look into that ...
> >
> > Regarding the original questions for TIMER_AFTER_URL_SLEEP, I am
> > trying to increase the number of users/conections (5000+) but keep the
> > BW low since my webserver can only support 100Mbps, and I thought
> > increasing the above timer would help (2 sec), but it seems like the
> > num. of users seems to be very low compared to what i have set it to.
> > Some users just dont seem to send requests for a long time (a lot more
> > than 2 sec), looking at tcpdump.
> >
> > What do you think could be problems. Can you suggest any other way to
> > achieve the above test setup. I dont want to use the
> > TRANSFER_RATE_LIMIT since I want the clients to fetch it at full BW.
> >
>
> Talking in general may be 3 sources of problem:
> a) client load side;
> b) network bottleneck, including NATs, Firewall limits, etc;
> c) web-server side.
>
> If you suspect, that the problem is on the side of curl-loader, please,
>  go through the procedure described in FAQs  here:
>
> http://curl-loader.sourceforge.net/doc/faq.html#big-load
>
> It may be e.g. a limit of open descriptors at your client computer or at
> server, etc problems.
>

Hello Robert,

I will look into those issues. One more thing I noticed was that for
different bind addresses its  using the same connection. Is this
expected?. Or should different addresses use a new connection
irrespective of the -r options.

Here is a log:

0 1 (12.0.0.1)  :== Info: About to connect() to 172.16.55.200 port 80 (#0)
: eff-url: , url:
0 1 (12.0.0.1)  :== Info:   Trying 172.16.55.200... : eff-url: , url:
0 1 (12.0.0.1)  :== Info: Bind local address to 12.0.0.1
: eff-url: , url:
0 1 (12.0.0.1)  :== Info: Local port: 38494
: eff-url: , url:
0 1 (12.0.0.1)  :== Info: Connected to 172.16.55.200 (172.16.55.200)
port 80 (#0)
: eff-url: , url:
0 1 (12.0.0.1)  => Send header: eff-url: , url:
0 1 (12.0.0.1)  <= Recv header: eff-url: , url:
0 1 (12.0.0.1) :!! 200 OK: eff-url: , url:
0 1 (12.0.0.1)  <= Recv header: eff-url: , url:
...
0 1 (12.0.0.1)  <= Recv header: eff-url: , url:
0 1 (12.0.0.1)  <= Recv data: eff-url: , url:
...
0 1 (12.0.0.1)  <= Recv data: eff-url: , url:
0 1 (12.0.0.1)  :== Info: Connection #0 to host 172.16.55.200 left intact
: eff-url: , url:
0 2 (12.0.0.2)  :== Info: Re-using existing connection! (#0) with host
172.16.55.200
: eff-url: , url:
0 2 (12.0.0.2)  :== Info: Connected to 172.16.55.200 (172.16.55.200)
port 80 (#0)
: eff-url: , url:
0 1 (12.0.0.1)  :== Info: About to connect() to 172.16.55.200 port 80 (#1)

Here 12.0.0.2 seems to be using the same connection as for 12.0.0.1

Thanks for your help.

-- Pranav

> If you have a multi-core or multi-cpu at the curl-loader linux computer, you
> can effectively
> increase your loading power, please use -t 2 or -t 4 options according to
> the number of cores/processors.
>
> --
>
>
> Sincerely,
>  Robert Iakobashvili
> "Light will come from Jerusalem"
> ...........................................................
> http://curl-loader.sourceforge.net
> An open-source web testing and traffic generation.
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> curl-loader-devel mailing list
> cur...@li...
> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel
>
>



-- 

------------------------------
http://pd.dnsalias.org