httpd-test-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Watch" <wa...@mail.deac.lv>
Subject Re: flood and memory
Date Tue, 24 Aug 2004 13:08:05 GMT
Hi.

>>   while using flood with 40MB config file,
>
>That's quite a size. Can you give more details on it? In particular how
many
>url's/url lists do you have, and how many farmers are running them in
>parallel.

here is more information that you requested.

root@actest1:~/httpd-test/flood# ls -alh mainconf.xml
-rw-r--r--  1 root root 39M 2004-08-16 17:20 mainconf.xml
root@actest1:~/httpd-test/flood# grep "<urllist>" mainconf.xml |wc -l
109
root@actest1:~/httpd-test/flood# grep "<url " mainconf.xml |wc -l
521393
root@actest1:~/httpd-test/flood# grep "<profile>" mainconf.xml |wc -l
109
root@actest1:~/httpd-test/flood# grep "<farmer>" mainconf.xml |wc -l
109

Basically, there are 109 different web's (like www.web1.com, www.web2.com,
etc.) and each web has list of url's, own profile, own farmer. All farmers
are placed into one "<farm>".

I started to divide that config file in to smaller ones. First one 4.8MB
survived, second one is 2.1MB and still takes all memory. Here are more
details on it.

root@actest1:/home/private# ls -alh mainconf.xml
-rw-r--r--  1 root root 2.1M 2004-08-17 15:47 mainconf.xml
root@actest1:/home/private# grep "<urllist>" mainconf.xml |wc -l
17
root@actest1:/home/private# grep "<url " mainconf.xml |wc -l
30144
root@actest1:/home/private# grep "<profile>" mainconf.xml |wc -l
17
root@actest1:/home/private# grep "<farmer>" mainconf.xml |wc -l
17
root@actest1:/home/private# grep "\"GET\"" mainconf.xml |wc -l
30045
root@actest1:/home/private# grep "\"POST\"" mainconf.xml |wc -l
85
root@actest1:/home/private# grep "\"HEAD\"" mainconf.xml |wc -l
0

>You mean: 'takes the client down', yes? The server can go down under heavy
>load, and you schould use other performance related tools to find out why.
>
>If you happen to run HTTP server and flood on the same machine, then this
is
>not such a good idea. With that big config file you are sure to have flood
and
>http daemon race for resources (which distorts overall results).

Http server is on another machine, it works fine. And flood has it's own
box, without anything else running on it. Only one process - flood - takes
all memory (ram and swap) and when there is nothing left, kernel kills the
flood process.

>Look at your flood source tree, find file 'config.h' (top source dir) and
>check for define FLOOD_VERSION.

root@actest1:~/httpd-test/flood# grep FLOOD_VERSION config.h
#define FLOOD_VERSION "1.1"

regards,
Jacek Prucia


Mime
View raw message