Live data from Hacker News

Tell HN: Have a look at Varnish

news.ycombinator.com

1–10 of 24 posts

Tell HN: Have a look at Varnish

#1
Hey Everyone!

I just wanted to share with you the link to an incredible HTTP accelerator: http://varnish-cache.org/

We've been testing a lot of different stacks for our startup (Tyba) and using NGINX (behind) + Varnish (upfront) has allowed us to go from 9 reqs/sec (loading a Wordpress site) to 2500 reqs/sec.

I know it's not a novelty but I wanted to share it in the hope it helps the few people who don't know about it.

Kind regards,

Eiso

Re: Tell HN: Have a look at Varnish

#3
Agreed, varnish is awesome, we use it on a home-brew CDN and it has been a fantastic experience so far.

Also, the guy that wrote it (Poul Henning-Kamp) is very responsive when it comes to answering questions or fixing issues, they have an IRC channel at #varnish on irc.linpro.no.

Definitely a piece of software worth looking in to when your website gets bigger.

Re: Tell HN: Have a look at Varnish

#7
post #6
post #5

Why would Varnish be required in that situation if you're already running nginx which is perfectly capable of caching a simple wordpress site in the same manner.

I don't think it's required, but, really, why wouldn't you be running varnish? It's just amazing.

Because it doesn't add anything useful to the mix - nginx's cache works just fine.

Re: Tell HN: Have a look at Varnish

#8
post #4

Agreed, nginx+varnish (optionally on top of an existing apache setup) seems to be best practice right now for heavy traffic sites.

This might be most popular setup right now, but I wouldn't consider it the best practice. Why in the world would you use both nginx and varnish?

Re: Tell HN: Have a look at Varnish

#9
post #4

Agreed, nginx+varnish (optionally on top of an existing apache setup) seems to be best practice right now for heavy traffic sites.

This might be most popular setup right now, but I wouldn't consider it the best practice. Why in the world would you use both nginx and varnish?

Because until 0.7 nginx lacked a caching system, and so it made sense to use both. Now it doesn't.
Post reply on HN