Hi,

I'm a newbie to pound. Right now I'm doing a smallish load test with 3 
clients and about 50 requests a second to a pound server with 2 backends.

However, after the test has run for about minute and a half, I get an 
error message in the client (all 3 of them) saying that the pound 
service itself isn't contactable. I've set my clients to retry if they 
get this error message, so once they get this error, they retry (i.e. 
hit the pound server again) and the test keeps on working normally. I've 
set the pound config file so that the client and the servers  timeout 
(i.e. close/abort the connection) after 120 seconds. Each request only 
takes 0.05 seconds to complete so this is more than ample time.

When running the test, the CPU load on the pound server is minimal. Top 
shows the load average to be zero and pound is the only process that is 
running on the box. The pound server is running on a single CPU (AMD 
Athlon(tm) 64 Processor 3000+ ) box with 2gig of memory.

I've also tried running this load test using another method to 
distribute the load (i.e. bypassing the pound server) to the 2 backends. 
In this case, the load test is successful and I don't get this error 
message.

If it helps, the client isn't a web browser. I'm using pound to direct 
requests from delphi clients to dephi soap services.

Any thoughts on why this may be happening?

Thanks for your help.

Cheers,
Kaye.

On Thu, 2007-06-07 at 08:17 +1000, Kaye Ng wrote:[...]

You may be running into system/network parameter limits, such as allowed
number of open files or network buffers. Have a close look at your
settings.[...]

Thanks for your help. I discovered that I was running into system
limits on the client box. I have reset the limits and have run the test
again successfully.

Cheers,
Kaye.

Robert Segall wrote:

  On Thu, 2007-06-07 at 08:17 +1000, Kaye Ng wrote:
  
  
    Hi,

I'm a newbie to pound. Right now I'm doing a smallish load test with 3 
clients and about 50 requests a second to a pound server with 2 backends.

However, after the test has run for about minute and a half, I get an 
error message in the client (all 3 of them) saying that the pound 
service itself isn't contactable. I've set my clients to retry if they 
get this error message, so once they get this error, they retry (i.e. 
hit the pound server again) and the test keeps on working normally. I've 
set the pound config file so that the client and the servers  timeout 
(i.e. close/abort the connection) after 120 seconds. Each request only 
takes 0.05 seconds to complete so this is more than ample time.

When running the test, the CPU load on the pound server is minimal. Top 
shows the load average to be zero and pound is the only process that is 
running on the box. The pound server is running on a single CPU (AMD 
Athlon(tm) 64 Processor 3000+ ) box with 2gig of memory.

I've also tried running this load test using another method to 
distribute the load (i.e. bypassing the pound server) to the 2 backends. 
In this case, the load test is successful and I don't get this error 
message.

If it helps, the client isn't a web browser. I'm using pound to direct 
requests from delphi clients to dephi soap services.

Any thoughts on why this may be happening?

Thanks for your help.
    
  
  
You may be running into system/network parameter limits, such as allowed
number of open files or network buffers. Have a close look at your
settings.