|
|
| Line 1: |
Line 1: |
| {{Ebuild | | {{Ebuild |
| |Summary=Varnish is a state-of-the-art, high-performance HTTP accelerator | | |Summary=Sublime Text is an advanced commercial text editor. |
| |CatPkg=www-servers/varnish | | |CatPkg=app-editors/sublime-text |
| |Homepage=https://www.varnish-cache.org/ | | |Maintainer=Oleg, |
| | |Homepage=http://sublimetext.com |
| }} | | }} |
| '''Varnish''' is a Web cache and HTTP accelerator. Varnish will either serve cached content, or retrieve content from the server, and cache it. Varnish cache will reduce I/O pressure on Web servers.
| | Sublime Text is a very complete text editor with lots of features, and support for plugins. It's free, but often shows a popup showing that's unregistered, so you can purchase the license for USD$70. |
|
| |
|
| ==Install== | | == Install == |
| ===Emerge===
| | First, you must have installed [[Package:Layman|Layman]] with Git support. Then, add the overlay ''sublime-text'': |
|
| |
|
| Install {{Package|www-servers/varnish}}:
| | <console>###i## layman -a sublime-text</console> |
| <console>###i## emerge www-servers/varnish</console> | |
|
| |
|
| ==Configuration==
| | Now, install the version you want. For the version 2: |
| | <console>###i## emerge -av sublime-text:2</console> |
|
| |
|
| {{note|as your varnish is local to your server, your server needs to be aware that it is behind a proxy, and configured for [http://en.wikipedia.org/wiki/X-Forwarded-For x-forwarded-for] or similar to fetch real users IP addresses instead of displaying 127.0.0.1 or localhost.}}
| | For the version 3 (default): |
| | <console>###i## emerge -av sublime-text:3</console> |
|
| |
|
| Configuration is controlled by /etc/varnish/default.vcl & /etc/conf.d/varnishd
| | You can have installed both versions, so you must install it with the USE flag ''multislot'', that also brings the package eselect-sublime. |
| | |
| {{file|name=/etc/varnish/default.vcl|desc=varnish configuration file|body=
| |
| vcl 4.0;
| |
| backend default {
| |
| .host = "127.0.0.1";
| |
| .port = "8080";
| |
| }
| |
| }}
| |
| | |
| {{file|name=/etc/conf.d/varnishd|desc=varnish configuration file|body=
| |
| VARNISHD="/usr/sbin/varnishd"
| |
| VARNISHADM="/usr/bin/varnishadm"
| |
| CONFIGFILE="/etc/varnish/default.vcl"
| |
| VARNISHD_OPTS="-a 127.0.0.1:80"
| |
| VARNISHD_OPTS="${VARNISHD_OPTS} -u varnish -g varnish"
| |
| }}
| |
| | |
| Varnish will fetch data from localhost:8080 and serve accelerated proxy data on localhost:80
| |
| | |
| === [https://www.varnish-cache.org/docs/4.0/users-guide/increasing-your-hitrate.html Achieving a high hit rate] ===
| |
| | |
| === c10k ===
| |
| For 10,000 concurrent connections -- or not -- a few configuration settings control the power of varnish. If you're having varnish directly serve to the outside world, dial back concurrency to say 50 or 100 connections per IP. You must take into account corporations and universities hammering several connections from a singular IP. c10k is useful information for if varnish is behind a load balancer such as pound, nginx, or tengine, and all requests are internal and local.
| |
| | |
| {{file|name=/etc/conf.d/varnishd|desc=varnish concurrency settings|body=
| |
| VARNISHD_OPTS="-a 127.0.0.1:80 -p thread_pool_min=20 -p thread_pool_max=1000 -p thread_pool_add_delay=2 -s malloc,700M"
| |
| }}
| |
| | |
| {{file|name=/etc/varnish/default.vcl|desc=varnish concurrency settings|body=
| |
| backend default {
| |
| .host = "127.0.0.1";
| |
| .port = "8080";
| |
| .connect_timeout = 600s;
| |
| .first_byte_timeout = 600s;
| |
| .between_bytes_timeout = 600s;
| |
| .max_connections = 10000;
| |
| # .port = "80" led to issues with competing for the port with apache.
| |
| }
| |
| }}
| |
| | |
| == Boot Service ==
| |
| | |
| To start varnish immediately:
| |
| <console>###i## rc-service varnishd start</console>
| |
| | |
| To start varnish at boot:
| |
| <console>###i## rc-update add varnishd default</console>
| |
| | |
| == Verification ==
| |
| To verify that your traffic is going through varnish, and see if you're getting hits or misses:
| |
| <console>$##i## curl -I http://www.funtoo.org/Welcome</console>
| |
| | |
| == Benchmarking ==
| |
| {{package|app-admin/apache-tools}} apache benchmark can show the power of varnish. The examples shown are running 500 requests with concurrency of 100 hits.
| |
| | |
| ;Example 1: ab against a 3 worker cluster mode puma server
| |
| <console>###i## ab -n 500 -c 100 http://127.0.0.1:3000/index.html | grep Request</console>
| |
| Requests per second: 110.92 [#/sec] (mean)
| |
| | |
| ;Example 2: ab against the same server served through varnish
| |
| <console>###i## ab -n 500 -c 100 http://127.0.0.1/index.html | grep Request</console>
| |
| Requests per second: 10268.42 [#/sec] (mean)
| |
| | |
| == SSL support ==
| |
| Varnish does not support ssl. There are packages to get around this limitation:
| |
| * {{package|net-misc/stunnel}}
| |
| * {{package|www-servers/pound}}
| |
| | |
| == Media ==
| |
| {{#widget:YouTube16x9|id=JEF6_XC-2ZU}}
| |
| {{EbuildFooter}} | | {{EbuildFooter}} |
