Poor #requests/second performance

[Kristian Lyngstol]

On Tue, Jun 02, 2009 at 08:10:06AM +0200, Andreas Jung wrote:
> Output of varnishstat:

(greedy-snipping)

Seeing as how you're testing with only a concurrency of 10, I doubt thread
startup is a big issue, but nevertheless, 12 threads is too low if you
intend to use this for production. I advice setting thread_pool_min to
reflect your actual expected load.

I also see a few expiries, it's not really easy to tell from varnishstat
what is causing the slowdowns, but it I would try setting up grace to
ensure that cache misses don't drag down a significant number of threads.

However, with only 10 concurrent requests, even one request going to the
backend will cause a significant hit to the requestrate. To solve this,
you'll have to either increase the concurrency of the test and/or increase
the lifespan of the cached objects.

Other than that, varnishstat -1 and some tinkering with varnishtop could
further track down the lousy performance you're seeing.

-- 
Kristian Lyngstøl
Redpill Linpro AS
Tlf: +47 21544179
Mob: +47 99014497
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20090602/88a77281/attachment-0003.pgp>