Khalad

You say you're using pound in front of a .NET server. Can you do manage your
site using Visual Studio (ie using Front Page extensions) through Pound?

If so would you mind posting what version of pound and what config you use
as I would be interested since I have not had much success. It would be much
appreciated.

Regards 
Mike

-----Original Message-----
From: Khaled Hassounah [mailto:khassounah(at)gmail.com] On Behalf Of Khaled
Hassounah
Sent: Monday, 30 April 2007 9:34 AM
To: pound(at)apsis.ch
Subject: [Pound Mailing List] blocked requests with increased concurrency

Hello all,

I setup a pound server in front of our .NET server (which we're
transitioning from) and ran some tests to see whether our QPS and
responsiveness were affected. The results showed a weird behavior at
high concurrency.

Here are the results: http://208.109.51.74/share/performance_tests.html

Three test sets. One at low concurrency (3 threads), one at medium (10
threads) and one at high (30 threads). Each test set included a run
directly against the web server, and one through pound.

At low concurrency, requests per seconds, and time per request were very
similar between direct and pound. When I ran with 10 threads, I noticed
that the numbers starting differing, but that while 98% of the requests
had a similar time per request, about 2% took more than 5 seconds!
Things started getting worse with the higher concurrency test. At 30
threads, At least 5% of the requests were taking longer than 5 seconds
to complete.

I am using ab for the tests, and all commands looked like: ab -c 30 -n
3000 http://pound/

It seems to me like some responses are being held hostage while others
are being served. Is that expected? This is somewhat concerned, as we do
see averages exceeding 20 requests for parts of the day.

Any insight would be appreciated. I like pound a lot, but this is very
concerning.

Khaled

-- 
To unsubscribe send an email with subject 'unsubscribe' to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.
http://www.apsis.ch/pound/pound_list/archive/2007/2007-04/1177889635000

You probably have to keep management to a separate IP not bound to pound

And use pound only for the requests. 

Just a nudge in the right direction. 

Can you set FP to use a management IP dedicated to the main server? Your
going to need to replicate content to the other servers. 

Any point in balancing the management? I assume it's the content that needs
the load balancing. 
 
Thank you,
Kiriki Delany









 

-----Original Message-----
From: Mike Withers [mailto:m.withers(at)uws.edu.au] 
Sent: Monday, April 30, 2007 5:13 PM
To: 'Khaled Hassounah'
Cc: pound(at)apsis.ch
Subject: RE: [Pound Mailing List] blocked requests with increased
concurrency

Khalad

You say you're using pound in front of a .NET server. Can you do manage your
site using Visual Studio (ie using Front Page extensions) through Pound?

If so would you mind posting what version of pound and what config you use
as I would be interested since I have not had much success. It would be much
appreciated.

Regards 
Mike

-----Original Message-----
From: Khaled Hassounah [mailto:khassounah(at)gmail.com] On Behalf Of Khaled
Hassounah
Sent: Monday, 30 April 2007 9:34 AM
To: pound(at)apsis.ch
Subject: [Pound Mailing List] blocked requests with increased concurrency

Hello all,

I setup a pound server in front of our .NET server (which we're
transitioning from) and ran some tests to see whether our QPS and
responsiveness were affected. The results showed a weird behavior at
high concurrency.

Here are the results: http://208.109.51.74/share/performance_tests.html

Three test sets. One at low concurrency (3 threads), one at medium (10
threads) and one at high (30 threads). Each test set included a run
directly against the web server, and one through pound.

At low concurrency, requests per seconds, and time per request were very
similar between direct and pound. When I ran with 10 threads, I noticed
that the numbers starting differing, but that while 98% of the requests
had a similar time per request, about 2% took more than 5 seconds!
Things started getting worse with the higher concurrency test. At 30
threads, At least 5% of the requests were taking longer than 5 seconds
to complete.

I am using ab for the tests, and all commands looked like: ab -c 30 -n
3000 http://pound/

It seems to me like some responses are being held hostage while others
are being served. Is that expected? This is somewhat concerned, as we do
see averages exceeding 20 requests for parts of the day.

Any insight would be appreciated. I like pound a lot, but this is very
concerning.

Khaled

-- 
To unsubscribe send an email with subject 'unsubscribe' to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.
http://www.apsis.ch/pound/pound_list/archive/2007/2007-04/1177889635000


-- 
To unsubscribe send an email with subject 'unsubscribe' to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.
http://www.apsis.ch/pound/pound_list/archive/2007/2007-05/1177978406000

Mike,

We are actually a linux shop, so we don't use frontpage. As to why our
site runs on .NET, that is a long story only told after 6pm and with a
beer in hand :)

Sorry I couldn't help.

Khaled

Mike Withers wrote:
> Khalad
>
> You say you're using pound in front of a .NET server. Can you do manage your
> site using Visual Studio (ie using Front Page extensions) through Pound?
>
> If so would you mind posting what version of pound and what config you use
> as I would be interested since I have not had much success. It would be much
> appreciated.
>
> Regards 
> Mike
>   

Does anyone have any ideas on where to start looking for an answer?

Khaled

Khaled Hassounah wrote:
> Hello all,
>
> I setup a pound server in front of our .NET server (which we're
> transitioning from) and ran some tests to see whether our QPS and
> responsiveness were affected. The results showed a weird behavior at
> high concurrency.
>
> Here are the results: http://208.109.51.74/share/performance_tests.html
>
> Three test sets. One at low concurrency (3 threads), one at medium (10
> threads) and one at high (30 threads). Each test set included a run
> directly against the web server, and one through pound.
>
> At low concurrency, requests per seconds, and time per request were very
> similar between direct and pound. When I ran with 10 threads, I noticed
> that the numbers starting differing, but that while 98% of the requests
> had a similar time per request, about 2% took more than 5 seconds!
> Things started getting worse with the higher concurrency test. At 30
> threads, At least 5% of the requests were taking longer than 5 seconds
> to complete.
>
> I am using ab for the tests, and all commands looked like: ab -c 30 -n
> 3000 http://pound/
>
> It seems to me like some responses are being held hostage while others
> are being served. Is that expected? This is somewhat concerned, as we do
> see averages exceeding 20 requests for parts of the day.
>
> Any insight would be appreciated. I like pound a lot, but this is very
> concerning.
>
> Khaled
>
>