From: eldy <> Date: Fri, 25 Oct 2002 17:13:04 +0000 (+0000) Subject: Updated documentation X-Git-Tag: AWSTATS_5_1_RELEASE~4 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fb2ade1bd532ee5070684aa0cc30a71c441650fe;p=thirdparty%2FAWStats.git Updated documentation --- diff --git a/docs/awstats_benchmark.html b/docs/awstats_benchmark.html index 0ac65111..62d48d3a 100644 --- a/docs/awstats_benchmark.html +++ b/docs/awstats_benchmark.html @@ -74,25 +74,26 @@ So, have a look at the following chart to:
This is examples of frequency/parameters you should use to have a good use of AWStats:

- - - - - - - - - - - - - + + + + + + + + + + + + +
Your Web site sizeRecommended values for parametersRecommended update frequency
(Rotate log delay)		Memory required**Duration***
DNSLookup*
0 - 1,000 visits/month1Once a week
Log files are 0-3 MB
10000 lines to process		<4 MB<2mn
0Once a month
Log files are 0-12 MB
40000 lines to process		<4 MB<20s.
1,000 - 10,000 visits/month1Every 12 hours
Log files are 1-2 MB
660-6600 lines		4-8 MB1-2mn
0Once a week
Log files are 3-30 MB
10000-100000 lines		4-8 MB5-50s
10,000 - 50,000 visits/month1Every 4 hours
Log files are 1-4 MB
2200-11000 lines		8-16 MB1-4mn
0Once a day
Log Files are 4-20 MB
13000-65000 lines		8-16 MB10-40s
50,000 - 250,000 visits/month1Every hour
Log Files are 1-4 MB
2700-14000 lines		16-64 MB2-4mn
0Every 6 hours
Log Files are 5-25 MB
17000-80000 lines		16-64 MB20-80s
250,000 - 1,000,000 visits/month0Every hour
Log Files are 4-16 MB
14000-56000 lines		64-256 MB30-120s
1,000,000 - 5,000,000 visits/month0AWStats is not a good choice for such web sites. Try a tool with less features but faster like Analog
+5,000,000 visits/month0AWStats is not a good choice for such web sites. Try a tool with less features but faster like Analog
Your Web site sizeRecommended values for parametersRecommended update frequency
(Rotate log delay)		Memory required**Duration***
DNSLookup*URLWithQueryURLReferrerWithQuery
0 - 1,000 visits/month10 or 10 or 1Once a week
Log files are 0-3 MB
10000 lines to process		<4 MB<2mn
0 (or 2)0 or 10 or 1Once a month
Log files are 0-12 MB
40000 lines to process		<4 MB<20s.
1,000 - 10,000 visits/month10 or 10 or 1Every 12 hours
Log files are 1-2 MB
660-6600 lines		4-8 MB1-2mn
0 (or 2)0 or 10 or 1Once a week
Log files are 3-30 MB
10000-100000 lines		4-8 MB5-50s
10,000 - 50,000 visits/month10 or 10 or 1Every 4 hours
Log files are 1-4 MB
2200-11000 lines		8-16 MB1-4mn
0 (or 2)0 or 10 or 1Once a day
Log Files are 4-20 MB
13000-65000 lines		8-16 MB10-40s
50,000 - 250,000 visits/month100 or 1Every hour
Log Files are 1-4 MB
2700-14000 lines		16-64 MB2-4mn
0 (or 2)00 or 1Every 6 hours
Log Files are 5-25 MB
17000-80000 lines		16-64 MB20-80s
250,000 - 1,000,000 visits/month0 (or 2)00Every hour
Log Files are 4-16 MB
14000-56000 lines		64-256 MB30-120s
1,000,000 - 5,000,000 visits/month0 (or 2)AWStats is not a good choice for such web sites. Try a tool with less features but faster like Analog
+5,000,000 visits/month0AWStats is not a good choice for such web sites. Try a tool with less features but faster like Analog
-* You should set DNSLookup parameter to 0 if
+* You should set DNSLookup parameter to 0 (or 2) if
      - reverse DNS lookup is already done in your log file
      - or if you don't need the "domain/countries" report
      - or if your web site has more than 250,000 visits a month.
-** Free memory required for update process (in MB). Warning: If you use the URLWithQuery option, this value is doubled.
+** Free memory required for update process (in MB).
+Warning: If you use the URLWithQuery or URLReferrerWithQuery option, this value can be dramatically increased.
*** Duration is with Athlon 1GHz/128Mb and LogFormat=1.

@@ -105,6 +106,11 @@ Note that with DNSLookup disabled if you still want to have the 'country/domain' in your log file are already resolved (need to setup your web server to do so, your web server will be slowed). Without DNSLookup, log analyze speed can be increased by 10 to 100 times.
+- Use carefully parameters URLWithQuery and URLReferrerWithQuery. +Let them set to 0 if you don't know what they means.
+ +- Be sure that your HostAliases parameter list is complete.
+ - Rotate your log (See FAQ-SET500) and launch AWStats more often (from crontab or a scheduler, See FAQ-SET550). The more often you launch AWStats, the less AWStats has new lines in log to process. This solve also the ActiveState memory problem (see next advice).