Re: Curl-loader results vary from time to time
Status: Alpha
Brought to you by:
coroberti
From: alo s. <asi...@ic...> - 2008-10-30 13:52:16
|
Hi Robert, I have copied the content of conf file below, ########### GENERAL SECTION ################################ BATCH_NAME=SAH10000r5 CLIENTS_NUM_MAX = 10000 CLIENTS_NUM_START = 50 CLIENTS_RAMPUP_INC= 50 INTERFACE=eth0 NETMASK=24 IP_ADDR_MIN=10.0.1.240 IP_ADDR_MAX=10.0.1.240 CYCLES_NUM= 1 URLS_NUM=1 ########### URL SECTION ################################## ### Login URL - only once for each client # GET-part URL= http://xx.x.x.x:pppp/main URL_SHORT_NAME="Login-GET" #URL_DONT_CYCLE = 1 REQUEST_TYPE=GET TIMER_URL_COMPLETION = 0 # In msec. Now it is enforced by cancelling url fetch on timeout TIMER_AFTER_URL_SLEEP = 0 # POST-part #URL="" #URL_USE_CURRENT= 1 #URL_SHORT_NAME="Login-POST" #URL_DONT_CYCLE = 1 #USERNAME=admin #PASSWORD=your_password #REQUEST_TYPE=POST #FORM_USAGE_TYPE= SINGLE_USER #FORM_STRING= username=%s&password=%s # Means the same credentials for all clients/users #TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by cancelling url fetch on timeout #TIMER_AFTER_URL_SLEEP =500 Thanks, Alo alo sinnathamby wrote: > Hi Robert, > > Thanks for your immediate reply and appreciate it. I am looking at your > suggestions and in the mean time please find below the conf file for the > tests that i run, > Greatly appreciate your help. > > Thanks, > Alo > > ########### GENERAL SECTION ################################ > BATCH_NAME=SAH10000r5 > CLIENTS_NUM_MAX = 10000 > CLIENTS_NUM_START = 50 > CLIENTS_RAMPUP_INC= 50 > INTERFACE=eth0 > NETMASK=24 > IP_ADDR_MIN=10.0.1.240 > IP_ADDR_MAX=10.0.1.240 > CYCLES_NUM= 1 > URLS_NUM=1 > > ########### URL SECTION ################################## > > ### Login URL - only once for each client > > # GET-part > URL= http://xx.x.x.x:pppp/main > URL_SHORT_NAME="Login-GET" > #URL_DONT_CYCLE = 1 > REQUEST_TYPE=GET > TIMER_URL_COMPLETION = 0 # In msec. Now it is enforced by cancelling url > fetch on timeout > TIMER_AFTER_URL_SLEEP = 0 > > # POST-part > #URL="" > #URL_USE_CURRENT= 1 > #URL_SHORT_NAME="Login-POST" > #URL_DONT_CYCLE = 1 > #USERNAME=admin > #PASSWORD=your_password > #REQUEST_TYPE=POST > #FORM_USAGE_TYPE= SINGLE_USER > #FORM_STRING= username=%s&password=%s # Means the same credentials for > all clients/users > #TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is > enforced by cancelling url fetch on timeout > #TIMER_AFTER_URL_SLEEP =500 > > > > > > > > Robert Iakobashvili wrote: > >> Hi Alo Sinnathamby, >> >> On Wed, Oct 29, 2008 at 10:04 PM, alo sinnathamby >> <asi...@ic... <mailto:asi...@ic...>> wrote: >> >> Dear support team, >> >> CURL-LOADER VERSION: 0.46 >> >> HW DETAILS: CPU/S and memory are must: >> x86_64 x86_64 x86_64 GNU/Linux >> OS: CentOS release 5.2 (Final) >> CPU: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz >> Ram: 2 Gigabytes DDR2 >> >> LINUX DISTRIBUTION and KERNEL (uname -r): CentOS release 5.2 (Final) >> >> GCC VERSION (gcc -v): >> >> COMPILATION AND MAKING OPTIONS (if defaults changed): >> >> COMMAND-LINE: >> >> CONFIGURATION-FILE (The most common source of problems): >> Place the file inline here: >> >> Thank you for PRF. >> >> You missed to place your configuration file, wich >> is essential for any judgement, >> >> >> >> >> QUESTION/ SUGGESTION/ PATCH: >> >> I have installed curl-loader on a testing client machine. i tried to >> test a home page of a website which is running with tomcat. the tomcat >> server system is: >> x86_64 x86_64 x86_64 GNU/Linux >> Operating System: CentOS release 5 (Final) >> CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz >> Ram: 4 Gigabytes DDR2 >> >> when i run 10 000 requests at different time intervals, i am getting >> different results as given below, >> >> 10 000 - run1 >> =============== >> Test total duration was 202 seconds and CAPS average 97: >> H/F >> Req:10000,1xx:0,2xx:9993,3xx:0,4xx:0,5xx:7,Err:0,T-Err:0,D:111ms,D-2xx:111ms,Ti:280361B/s,To:7425B/s >> H/F/S >> Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To:0B/s >> Operations: Success Failed >> Timed out >> URL0:Login-GET 150 9993 0 7 >> 0 0 >> >> >> 10 000 - run2 >> ============== >> Test total duration was 234 seconds and CAPS average 85: >> H/F >> Req:9773,1xx:0,2xx:9773,3xx:0,4xx:0,5xx:0,Err:227,T-Err:0,D:861ms,D-2xx:861ms,Ti:236413B/s,To:6264B/s >> H/F/S >> Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To:0B/s >> Operations: Success Failed >> Timed out >> URL0:Login-GET 7 9773 0 227 >> 0 0 >> >> >> 10 000 - run3 >> ============== >> Test total duration was 318 seconds and CAPS average 62: >> H/F >> Req:6183,1xx:0,2xx:6012,3xx:0,4xx:0,5xx:0,Err:3988,T-Err:0,D:6602ms,D-2xx:6602ms,Ti:106771B/s,To:2916B/s >> H/F/S >> Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To:0B/s >> Operations: Success Failed >> Timed out >> URL0:Login-GET 0 6012 3 3988 >> 0 0 >> >> >> Could you please let us know as how to fine tune it to get a >> consistent >> result. FYI: both the client and server are in the local network. >> >> >> I can only guess without the configuration file, that your server >> works really hard. Please, monitor the server-side performance. >> >> The reasons for errors could be seen in the log file. >> Please look into the <your-name>.log file. >> >> You can see at the reasons of errors, when adding to the command line -v. >> Most probably, your server gets saturated and does not handle >> TCP-connections. >> >> >> You can also try to recompile curl-loader with optimization and add more >> mem for TCP, file descriptors like here: >> http://curl-loader.sourceforge.net/doc/faq.html >> >> in the 7.2. How to run a really big load? >> >> Please, update me about your advances. >> >> >> >> -- >> 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. |