Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
f4f1e8ad
Commit
f4f1e8ad
authored
Oct 11, 2011
by
Lasse Karstensen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add short segment on VMs / OpenVZ
parent
3ede515d
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
21 additions
and
0 deletions
+21
-0
index.rst
doc/sphinx/tutorial/index.rst
+1
-0
virtualised.rst
doc/sphinx/tutorial/virtualised.rst
+20
-0
No files found.
doc/sphinx/tutorial/index.rst
View file @
f4f1e8ad
...
@@ -26,6 +26,7 @@ separate topic. Good luck.
...
@@ -26,6 +26,7 @@ separate topic. Good luck.
vary
vary
purging
purging
esi
esi
virtualised
advanced_backend_servers
advanced_backend_servers
handling_misbehaving_servers
handling_misbehaving_servers
advanced_topics
advanced_topics
...
...
doc/sphinx/tutorial/virtualised.rst
0 → 100644
View file @
f4f1e8ad
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.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment