r4863 - trunk/varnish-cache/doc/sphinx/tutorial

perbu at varnish-cache.org perbu at varnish-cache.org
Fri May 28 13:37:39 CEST 2010

Author: perbu
Date: 2010-05-28 13:37:39 +0200 (Fri, 28 May 2010)
New Revision: 4863

added varnishlog and varnishtop to increasing hitrate chapter

Modified: trunk/varnish-cache/doc/sphinx/tutorial/increasing_your_hitrate.rst
--- trunk/varnish-cache/doc/sphinx/tutorial/increasing_your_hitrate.rst	2010-05-28 10:55:08 UTC (rev 4862)
+++ trunk/varnish-cache/doc/sphinx/tutorial/increasing_your_hitrate.rst	2010-05-28 11:37:39 UTC (rev 4863)
@@ -10,16 +10,33 @@
 to get a high hitrate in Varnish.
 Note that you need a tool to see what HTTP headers fly between you and
-the web server. If you have Varnish the easiest might be to use
-varnishlog, but sometimes a separate tool makes sense. Here are the
-ones I use.
+the web server. If you have Varnish the easiest is to use varnishlog
+and varnishtop but sometimes a client-side tool makes sense. Here are
+the ones I use.
+Tool: varnistop
+You can use varnishtop to identify what URLs are hitting the backend
+the most. ``varnishtop -i txurl`` is a essential command. You can see
+some other examples of varnishtop usage in :ref:`tutorial-statistics`.
+Tool: varnishlog
+When you have identified the an URL which is frequently sent to the
+backend you can use varnishlog to have a look at the whole request.
+``varnishlog -c -o /foo/bar`` will give the whole (-o) requests coming
+from the client (-c) matching /foo/bar. 
 Tool: lwp-request
 lwp-request is part of The World-Wide Web library for Perl. It's
 couple of really basic programs that can execute a HTTP request and
-give you the result. I use two programs, GET and HEAD.
+give you the result. I mostly use two programs, GET and HEAD.
 vg.no was the first site to use Varnish and the people running Varnish
 there are quite cluefull. So its interesting to look at their HTTP

More information about the varnish-commit mailing list