Re: Curl-loader results vary from time to time

[alo s. <asi...@ic...>]

Hi Robert,

Thanks and greatly appreciate it. Your help is a timely help and Thanks 
a lot. We are looking at it 
http://curl-loader.sourceforge.net/high-load-hw/index.html, and trying 
to set up the same or equivalent environment.

In the mean time, this is my quick question,

*When we change CLIENTS_RAMPUP_INC, the run time differs to a great 
extent. So how can i determine the correct run time with respect to a 
given number of requests.*

For example (from my test runs):

case 1: when CLIENTS_RAMPUP_INC=50, the run time for 20000 requests are 
300 seconds

case 2: when CLIENTS_RAMPUP_INC=75, the run time for 20000 requests are 
200 seconds

case 3: when CLIENTS_RAMPUP_INC=100, it throws so many connection time 
out error.

Because of these different results, i am not able to determine the 
correct run time for any given number of requests. Our objective is to 
determine the load capability and run time for any given number of 
requests, say for an example 20000, 50000, 70000, 100000 requests.

Please render your valuable advice and Greatly appreciate your help.

Thanks,
Alo











Robert Iakobashvili wrote:
> Hi Alo,
>
> On Mon, Nov 3, 2008 at 8:33 PM, alo sinnathamby 
> <asi...@ic... <mailto:asi...@ic...>> wrote:
>
>     Hi Robert,
>
>     Thanks for your reply and appreciate it. I have upgraded the test
>     client's RAM from 2 gig to 4 gig and now it gives me a kind of
>     consistent result, though it varies a little. 
>
>
> Great!
>  
>
>     I have followed the FAQ
>     sec 7.2 recommendations but that didn't make any big difference.
>
>
> It means, that your system was short in memory as expected.
> 40K per virtual client!
>
>  
>
>     Now, i have another question: what is the best configuration for
>     testing
>     50 000, 60 000, 70 000, 100 000 requests. Currently i am using the
>     following configuration,
>
>
>     Operating System:    CentOS release 5.2 (Final)
>     CPU:    Intel(R) Core(TM)2 Duo CPU     E4600  @ 2.40GHz
>     Ram:    4 Gigabytes DDR2
>
>     My hosting server is:
>     Linux
>     Operating System:    CentOS release 5 (Final)
>     CPU:    Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
>     Ram:    4 Gigabytes DDR2
>
>     Please let me know the optimum and best configurations for testing
>     really big loads. The reason why i am asking this question is, when i
>     put CLIENTS_RAMPUP_INC=50, it takes more time but less failed. when i
>     put CLIENTS_RAMPUP_INC=75, it takes less time and more failed.
>     Alo
>
>
>
> What was the effect of running command line with option -t 4 ?
>
> Specifcally, I would recommend you *curl-loader - High Load HW *
> as explained in the link here:
> http://curl-loader.sourceforge.net/high-load-hw/index.html
>
> So, for 100 000 req/sec better to use a dual quad-core (a single 
> quad-core may be not enough)
> with 8 GB of checked memory.
>
> Please, pay attention, that your OS should support above 4 GB 
> addressing in a single
> process. We are using 64-bit Debian linux (lenny).
>
> I would recommend -t 4 or -t 8 options, not more than 15000 clients, 
> ramp rate could
> be 100, if more powerful CPUs used. Take care about the NEVENT 
> parameter as described
> in *curl-loader - High Load HW
> *
> Best wishes!
>
> Truly,
> Robert Iakobashvili, Ph.D.
> ......................................................................
> Assistive technology that understands you
> ......................................................................

NOTE: This message, and any attached files, contain information that is privileged, confidential, proprietary or otherwise protected from disclosure.  Any disclosure, copying or distribution of, or reliance upon, this message by anyone else is strictly prohibited.  If you received this communication in error, please notify the sender immediately by reply e-mail message or by telephone to one of the numbers above and deleting it from your computer.  Thank you.