Mailing List Archive: What to do best performance at varnish?

What to do best performance at varnish?

Jul 24, 2007, 12:21 AM

Post #1 of 3 (585 views)

Hello, list.

I would like to set the vernishd with best performance caching.
But I can't find any related documentation,(already saw man page)
So is there any recommendable config to improve the performance of
varnishd?
My system is linux(kernel 2.6, centos 4.x)

for example,
-. which Cache file size is required?
-. Dual CPU and large RAM would be good to performance?
-. which value is required VARNISH_MAX_THREADS, VARNISH_MIN_THREADS?
-. any sysctl tuning?

Thanks for your help in advance.

_________________________________________________________________
????? ??? ?? ????? http://phonebuddy.msn.co.kr/

What to do best performance at varnish? [ In reply to ]

phk at phk

Jul 24, 2007, 12:26 AM

Post #2 of 3 (559 views)

Permalink

We have very little experience with performance tuning yet, as very
few people need to do any, Varnish is very frugal with hardware
resources.

Make sure your cache file is big enough, making it too big won't cost
you anything, so don't worry about it.

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

What to do best performance at varnish? [ In reply to ]

des at linpro

Jul 24, 2007, 1:35 AM

Post #3 of 3 (568 views)

Permalink

"Monty Ree" <chulmin2 at hotmail.com> writes:
> - which Cache file size is required?

At least as large as your working set. Beyond that, you run into the
law of diminishing returns, unless you expect your working set to grow
over time.

> - Dual CPU and large RAM would be good to performance?

Yes.

> - which value is required VARNISH_MAX_THREADS, VARNISH_MIN_THREADS?

Leave them unchanged. Keep an eye on n_wrk_overflow and n_wrk_drop in
varnishstat; if they increase rapidly under normal working conditions,
increase thread_pool_max. If n_wrk_overflow increases but n_wrk_drop
doesn't, consider increasing thread_pool_min. If your traffic comes in
bursts, increasing thread_pool_timeout might help, but in most cases it
won't.

> - any sysctl tuning?

No more than is generally recommended for the amount of memory you have
and the amount of network traffic you expect.

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no