Updated documentation.

diff --git a/docs/awstats_benchmark.html b/docs/awstats_benchmark.html
index c4067d397ac37769a3c1eabeef9f7f3bdfdcb415..42cc10f20e729523ac304b10cfe17a75395462cd 100644 (file)
--- a/docs/awstats_benchmark.html
+++ b/docs/awstats_benchmark.html
@@ -44,7 +44,7 @@ AWStats speed depends on AWStats version and options/setup you use in configurat
 <b><u>This is benchmark results with AWStats version 5.1 and a common configuration:</u></b><br>\r
 <br>\r
 HARDWARE: Athlon 1 GHz / 128Mb<br>\r
-SOFTWARE: Windows 2000 / Perl 5.8<br>\r
+SOFTWARE: Windows 2000 / Perl 5.8 (Standard Perl, ActiveState is much slower)<br>\r
 CONFIG OPTIONS: <a href="awstats_config.html#LogFormat">LogFormat</a>=1, <a href="awstats_config.html#DNSLookup">DNSLookup</a>=0, <a href="awstats_config.html#URLWithQuery">URLWithQuery</a>=0, <a href="awstats_config.html#URLReferrerWithQuery">URLReferrerWithQuery</a>=0, No plugins<br>\r
 AVERAGE SPEED: <b>4500</b> lines by seconds<br>\r
 Other times for different kind of web sites sizes are shown later in this page...<br>\r
@@ -53,19 +53,18 @@ Other times for different kind of web sites sizes are shown later in this page..
 <br>\r
 <b><u>This is other important information to know:</u></b><br>\r
 <br>\r
-- A log file size is about <b>150</b> (NCSA common/CLF log files) to <b>300 times</b> (NCSA extended/XLF/ELF log files) its number of lines,<br>\r
-- A <b>30Mb file</b> = <b>100,000 lines</b> = <b>20,000 pages</b> (with 5 hits/page) = <b>2,500 visits</b> (with 8 pages/visits) => <b>75 seconds</b> (Athlon 1GHz)<br>\r
-- History files (resuming the log analyze) has the following size (one file a month) :\r
-<!-- 15Ko + 60*(1*719/720+100*1/720)*x + 100*y + 2*100*x*4/100 + 20*x*1.4*10*10*(2/100+1/100) -->\r
-<b>15000+160*x+100*y bytes</b> (where x is number of unique visitors a month and y is number of different pages on web sites)<br>\r
-WARNING ! All those data are average values for a common public site. Calculation rule can be seriously changed\r
-according to web server or AWStats configuration and web site content.<br>\r
+- A log file size is about <b>150</b> (NCSA common/CLF log files) to <b>320 times</b> (NCSA extended/XLF/ELF log files) its number of lines,<br>\r
+- <b>1,000 visits</b> = <b>8,000 pages</b> (with 8 pages/visits) = <b>64,000 lines</b> (with 8 hits/page) = <b>20 MB file</b> => <b>15 seconds</b> (Athlon 1GHz, Standard Perl 5.8)<br>\r
+- History files (resuming the log analysis) has the following size (one file a month) :\r
+<b>15000+90*x+100*y bytes</b> (where x is number of unique visitors a month and y is number of different pages on web sites)<br>\r
+WARNING ! All those data are average values for a common public site with default configuration.\r
+Calculation rule can be seriously changed according to web server or AWStats configuration and web site content.<br>\r
 \r
 <br>\r
-Don't forget that benchmarks of log analyzers are made without reverse DNS lookup\r
-because this depends on your system, networks and Internet and not on the\r
-log analyzer you use. And the reverse DNS lookup can take more than <b>95%</b> of time of a log analysis !<br>\r
-So, have a look at the following chart to:<br>\r
+Don't forget that benchmarks of log analyzers are made without reverse DNS lookup because DNS\r
+lookup is so slow (depending on Internet network and your system), that if enabled in AWStats\r
+configuration file, it would take more than <b>99%</b> of the time of a log analysis !\r
+Take a look at the following chart to:<br>\r
 - Get more real ideas on benchmarks results<br>\r
 - Get more information and advice on a good setup for your site.<br>\r
 \r
@@ -76,26 +75,26 @@ So, have a look at the following chart to:<br>
 <table border=1 cellspacing=0 cellpadding=2 style="font: 12px; arial,verdana">\r
 <tr bgcolor=#EEEEEE><td rowspan=2>Your Web site size</td><td colspan=3>Recommended values for parameters</td><td rowspan=2>Recommended update frequency<br>(Rotate log delay)</td><td rowspan=2>Memory required**</td><td rowspan=2>Duration***</td></tr>\r
 <tr bgcolor=#EEEEEE><td>DNSLookup*</td><td>URLWithQuery</td><td>URLReferrerWithQuery</td></tr>\r
-<tr><td rowspan=2>     0 -     1,000 visits/month</td><td>1</td><td>0 or 1</td><td>0 or 1</td><td>Once a week<br>Log files are 0-3 MB<br>10000 lines to process</td><td><4 MB</td><td><2mn</td></tr>\r
-<tr>                                                <td>0 (or 2)</td><td>0 or 1</td><td>0 or 1</td><td>Once a month<br>Log files are 0-12 MB<br>40000 lines to process</td><td><4 MB</td><td><20s.</td></tr>\r
-<tr><td rowspan=2> 1,000 -    10,000 visits/month</td><td>1</td><td>0 or 1</td><td>0 or 1</td><td>Every 12 hours<br>Log files are 1-2 MB<br>660-6600 lines</td><td>4-8 MB</td><td>1-2mn</td></tr>\r
-<tr>                                                <td>0 (or 2)</td><td>0 or 1</td><td>0 or 1</td><td>Once a week<br>Log files are 3-30 MB<br>10000-100000 lines</td><td>4-8 MB</td><td>5-50s</td></tr>\r
-<tr><td rowspan=2>10,000 -    50,000 visits/month</td><td>1</td><td>0 or 1</td><td>0 or 1</td><td>Every 4 hours<br>Log files are 1-4 MB<br>2200-11000 lines</td><td>8-16 MB</td><td>1-4mn</td></tr>\r
-<tr>                                                <td>0 (or 2)</td><td>0 or 1</td><td>0 or 1</td><td>Once a day<br>Log Files are 4-20 MB<br>13000-65000 lines</td><td>8-16 MB</td><td>10-40s</td></tr>\r
-<tr><td rowspan=2>50,000 -   250,000 visits/month</td><td>1</td><td>0</td><td>0 or 1</td><td>Every hour<br>Log Files are 1-4 MB<br>2700-14000 lines</td><td>16-64 MB</td><td>2-4mn</td></tr>\r
-<tr>                                                <td>0 (or 2)</td><td>0</td><td>0 or 1</td><td>Every 6 hours<br>Log Files are 5-25 MB<br>17000-80000 lines</td><td>16-64 MB</td><td>20-80s</td></tr>\r
-<tr><td>         250,000 - 1,000,000 visits/month</td><td>0 (or 2)</td><td>0</td><td>0</td><td>Every hour<br>Log Files are 4-16 MB<br>14000-56000 lines</td><td>64-256 MB</td><td>30-120s</td></tr>\r
-<tr><td>       1,000,000 - 5,000,000 visits/month</td><td colspan=6>AWStats is not a good choice for such web sites. Try a tool with less features but faster like <a href="http://www.analog.cx">Analog</a> or <a href="http://www.mrunix.net/webalizer/">Webalizer</a></td></tr>\r
+<tr><td rowspan=2>     0 -     1,000 visits/month</td><td>1</td><td>0 or 1</td><td>0 or 1</td><td>Once a day<br>Log files are 0-1 MB<br>2000 lines to process</td><td>4 MB</td><td>2mn</td></tr>\r
+<tr>                                                <td>0 (or 2)</td><td>0 or 1</td><td>0 or 1</td><td>Once a day<br>Log files are 0-1 MB<br>2000 lines to process</td><td>4 MB</td><td>1s</td></tr>\r
+<tr><td rowspan=2> 1,000 -    10,000 visits/month</td><td>1</td><td>0 or 1</td><td>0 or 1</td><td>Once a day<br>Log files are 1-10 MB<br>2000-20000 lines</td><td>4-8 MB</td><td>2-10mn</td></tr>\r
+<tr>                                                <td>0 (or 2)</td><td>0 or 1</td><td>0 or 1</td><td>Once a day<br>Log files are 1-10 MB<br>2000-20000 lines</td><td>4-8 MB</td><td>1-10s</td></tr>\r
+<tr><td rowspan=2>10,000 -    100,000 visits/month</td><td>1</td><td>0 or 1</td><td>0 or 1</td><td>Every 12 hours<br>Log files are 5-50 MB<br>10000-100000 lines</td><td>8-16 MB</td><td>5-50mn</td></tr>\r
+<tr>                                                <td>0 (or 2)</td><td>0 or 1</td><td>0 or 1</td><td>Every 12 hours<br>Log Files are 5-50 MB<br>10000-100000 lines</td><td>8-16 MB</td><td>5-50s</td></tr>\r
+<tr><td rowspan=2>100,000 -   500,000 visits/month</td><td>1</td><td>0</td><td>0 or 1</td><td>Every hour<br>Log Files are 4-16 MB<br>10000-50000 lines</td><td>16-64 MB</td><td>5-25mn</td></tr>\r
+<tr>                                                <td>0 (or 2)</td><td>0</td><td>0 or 1</td><td>Every hour<br>Log Files are 4-16 MB<br>10000-50000 lines</td><td>16-64 MB</td><td>5-25s</td></tr>\r
+<tr><td>         500,000 - 2,000,000 visits/month</td><td>0 (or 2)</td><td>0</td><td>0</td><td>Every hour<br>Log Files are 16-64 MB<br>50000-200000 lines</td><td>64-256 MB</td><td>25-120s</td></tr>\r
+<tr><td>       2,000,000 - 5,000,000 visits/month</td><td colspan=6>AWStats is not a good choice for such web sites. Try a tool with less features but faster like <a href="http://www.analog.cx">Analog</a> or <a href="http://www.mrunix.net/webalizer/">Webalizer</a></td></tr>\r
 <tr><td>      +5,000,000 visits/month</td><td colspan=6>AWStats is not a good choice for such web sites. Try a tool with less features but faster like <a href="http://www.analog.cx">Analog</a></td></tr>\r
 </table>\r
 * You should set <a href="awstats_config.html#DNSLookup">DNSLookup</a> parameter to 0 (or 2) if<br>\r
 &nbsp;&nbsp; &nbsp;&nbsp; - reverse DNS lookup is already done in your log file,<br>\r
 &nbsp;&nbsp; &nbsp;&nbsp; - or if your web site has more than 250,000 visits a month.<br>\r
 Note: Country report can works without reverse DNS lookup if plugin 'geoip' is enabled (faster and more accurate than reverse DNS lookup).<br>\r
-** Free memory required for update process (in MB).<br>\r
+** Free memory required for update process (in MB), not hardware memory installed.<br>\r
 Warning: If you use the <a href="awstats_config.html#URLWithQuery">URLWithQuery</a> or <a href="awstats_config.html#URLReferrerWithQuery">URLReferrerWithQuery</a> option, or forget\r
 to complete correctly <a href="awstats_config.html#URLQuerySeparators">URLQuerySeparators</a> for some sites, this value can be dramatically increased.<br>\r
-*** Duration is with Athlon 1GHz/128Mb and LogFormat=1.<br>\r
+*** Duration is with Athlon 1GHz/128Mb, Standard Perl 5.8 and LogFormat=1.<br>\r
 \r
 <br>\r
 <br>\r
@@ -107,10 +106,10 @@ be set to 0, or 2 to only use a DNS file resolver). Note that you still can have
 without DNS lookup enabled. For this you must enable the 'geoip' plugin. Without this plugin, 'Country'\r
 report will works only if hosts addresses in your log file are already resolved (need to setup your web\r
 server to do so, your web server will be slowed). With DNSLookup enabled, log analyze speed is decreased\r
-by 20 to 100 times.<br>\r
+by 40 to 100 times.<br>\r
 <img src="images/star.png"><img src="images/star.png"><img src="images/star.png"><img src="images/star.png">\r
-- Use carefully parameters <a href="awstats_config.html#URLWithQuery">URLWithQuery</a> and <a href="awstats_config.html#URLReferrerWithQuery">URLReferrerWithQuery</a>\r
-(Let them set to 0 if you don't know what they means) and check your web site URLs' syntax to know if you don't need to complete parameter <a href="awstats_config.html#URLQuerySeparators">URLQuerySeparators</a>.\r
+- Use carefully parameters <a href="awstats_config.html#URLWithQuery">URLWithQuery</a>, <a href="awstats_config.html#URLReferrerWithQuery">URLReferrerWithQuery</a> and <a href="awstats_config.html#URLWithAnchor">URLWithAnchor</a>\r
+(Let them set to 0 if you don't know what they means) and check your web site URLs' syntax to know if you don't need to complete the parameter <a href="awstats_config.html#URLQuerySeparators">URLQuerySeparators</a>.\r
 If you really need to use <a href="awstats_config.html#URLWithQuery">URLWithQuery</a>=1, check that <a href="awstats_config.html#URLWithQueryWithoutFollowingParameters">URLWithQueryWithoutFollowingParameters</a> is set properly.<br>\r
 <img src="images/star.png"><img src="images/star.png"><img src="images/star.png"><img src="images/star.png">\r
 - Be sure that your <a href="awstats_config.html#HostAliases">HostAliases</a> parameter list is complete.<br>\r