[experimental-ims] f4f1e8a Add short segment on VMs / OpenVZ

Geoff Simmons geoff at varnish-cache.org
Mon Jan 9 21:52:17 CET 2012


commit f4f1e8ad2e9ffff37a10c2bf673c2da65a54ece9
Author: Lasse Karstensen <lasse at varnish-software.com>
Date:   Tue Oct 11 09:59:00 2011 +0200

    Add short segment on VMs / OpenVZ

diff --git a/doc/sphinx/tutorial/index.rst b/doc/sphinx/tutorial/index.rst
index e0e5023..59fd94e 100644
--- a/doc/sphinx/tutorial/index.rst
+++ b/doc/sphinx/tutorial/index.rst
@@ -26,6 +26,7 @@ separate topic. Good luck.
 	vary
 	purging
 	esi
+	virtualised
 	advanced_backend_servers
         handling_misbehaving_servers
         advanced_topics
diff --git a/doc/sphinx/tutorial/virtualised.rst b/doc/sphinx/tutorial/virtualised.rst
new file mode 100644
index 0000000..ce4b9ad
--- /dev/null
+++ b/doc/sphinx/tutorial/virtualised.rst
@@ -0,0 +1,20 @@
+
+Running inside a virtual machine (VM)
+-------------------------------------
+
+It is possible, but not recommended for high performance, to run Varnish on virtualised 
+hardware.
+
+OpenVZ
+''''''
+
+If you are running on 64bit OpenVZ (or Parallels VPS), you must reduce the 
+maximum stack size before starting Varnish. The default allocates to much memory per thread, 
+which will make varnish fail as soon as the number of threads (==traffic) increases.
+
+Reduce the maximum stack size by running::
+
+    ulimit -s 256
+
+in the startup script.
+



More information about the varnish-commit mailing list