Re: TIMER_AFTER_URL_SLEEP question

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

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.

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.