Yes, the site have many concurent user.

Even more then 1000 concurent user, the bandwith usage for web up to 4 Mbps (mainly text display)

I just want to test it before implement the pound for load balance.

The backend work fine, when heavily load with many user, pound not respond.

 

After send the mail, I try to recompile pound with the new configuration of "ulimit"

And I test with 1000 for the "stress level (threads)", and 1 for the
"stress multiplier (sockets per threads)"

I open the test site, and the pound still manage to handle the request.

I will do some more testing, and check the error log in the pound.

 

But I have something in my mind, Is the effect of reconfigure the ulimit, may result after recompile the pound?

 

And about this, "You'd need to recompile the library to go beyond that" ---> Which library I should recompile? Could you explain me a little bit?

And what linux OS I should use?

 

Thanks..

On 3/7/06, Robert Segall <roseg@apsis.ch> wrote:

On Tue, 2006-03-07 at 11:17 +0000, Agustinus Mulyawan wrote:
> I have test the pound with web application stress tool,
> in the 500 for the "stress level (threads)", and 1 for the "stress
> multiplier (sockets per threads)"
> I assume it 500 user.
> I test it for a while, the pound manage to survive, but some lagging for the
> 1st open up the site..
> Then I try to test with 1000 for the "stress level (threads)", and 1 for the
> "stress multiplier (sockets per threads)"
> And the web show up this error messages, "503 Service Unavailable"
> in the pound log, i found this error (repeatedly)
>      pound pound: error copy server cont: Connection reset by peer
>      pound pound: error flush headers to 192.168.100.1 : Connection reset by
> peer
>      pound pound: error copy server cont: Connection timed out
>      pound pound: backend 192.168.0.251:80 create: Too many open file
>
> I had try to set the clients to 600, and set the ulimit
>
> [root@pound root]# ulimit -a
> core file size        (blocks, -c) unlimited
> data seg size         (kbytes, -d) unlimited
> file size             (blocks, -f) unlimited
> max locked memory     (kbytes, -l) unlimited
> max memory size       (kbytes, -m) unlimited
> open files                    (-n) 999999
> pipe size          (512 bytes, -p) 8
> stack size            (kbytes, -s) unlimited
> cpu time             (seconds, -t) unlimited
> max user processes            (-u) unlimited
> virtual memory        (kbytes, -v) unlimited
>
> what should I do so I can achieve the best performance ?
> do i need configure the sysctl?

At a 1000 concurrent requests you may be running into the pthread limit
of max threads. You'd need to recompile the library to go beyond that.

Given your log messages you may also have a problem with your back-ends:
are you sure they can actually deal with this sort of activity?

Do you actually expect that sort of load on your site?
--
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904


--
To unsubscribe send an email with subject 'unsubscribe' to pound@apsis.ch.
Please contact roseg@apsis.ch for questions.
http://www.apsis.ch/pound/pound_list/archive/2006/2006-03/1141191335000/1141750189000