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
9bef407d
Commit
9bef407d
authored
Aug 15, 2011
by
Per Buer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
more on bans, the lurker
parent
47e277b3
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
3 deletions
+12
-3
purging.rst
doc/sphinx/tutorial/purging.rst
+12
-3
No files found.
doc/sphinx/tutorial/purging.rst
View file @
9bef407d
...
...
@@ -89,9 +89,18 @@ they could issue::
Quite powerful, really.
Bans are checked when we hit an object in the cache, but before we
deliver it. *An object is only checked against newer bans*. If you have
a lot of objects with long TTL in your cache you should be aware of a
potential performance impact of having many bans.
deliver it. *An object is only checked against newer bans*.
Bans that only match against beresp.* are also processed by a
background worker threads called the *ban lurker*. The ban lurker will
walk the heap and try to match objects and will evict the matching
objects. How aggressive the ban lurker is can be controlled by the
parameter ban_lurker_sleep.
Bans that are older then the oldest objects in the cache are discarded
without evaluation. If you have a lot of objects with long TTL, that
are seldom accessed you might accumulate a lot of bans. This might
impact CPU usage and thereby performance.
You can also add bans to Varnish via HTTP. Doing so requires a bit of VCL::
...
...
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