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
4e529dad
Commit
4e529dad
authored
Feb 24, 2012
by
Lasse Karstensen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Use american english
parent
21beea85
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
0 deletions
+23
-0
virtualized.rst
doc/sphinx/tutorial/virtualized.rst
+23
-0
No files found.
doc/sphinx/tutorial/virtualized.rst
0 → 100644
View file @
4e529dad
Running Varnish in a virtualized environment
--------------------------------------------
It is possible, but not recommended for high performance, to run
Varnish on virtualized hardware. Reduced disk- and network performance
will reduce the performance a bit so make sure your system has good IO
performance.
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