Updated documentation

diff --git a/docs/awstats_benchmark.html b/docs/awstats_benchmark.html
index 00dfa34455e09efee1918fe9dfdc09d5914390a8..e191ea7a1d931d919e42d55b42020de8134b4317 100644 (file)
--- a/docs/awstats_benchmark.html
+++ b/docs/awstats_benchmark.html
@@ -38,18 +38,29 @@ AWStats update process must be ran frequently, so it's important to know what is
 speed to choose an optimum delay between each update process according to AWStats speed and\r
 the refresh rate you need to have.<br>\r
 AWStats speed depends on AWStats version and options/setup you use in configuration file.<br>\r
+\r
+<br>\r
+<br>\r
+<b><u>This is benchmark results with AWStats version 4.1 and a common configuration:</u></b><br>\r
 <br>\r
-<b><u>This is benchmark results with AWStats version 4.0 and a common configuration:</u></b><br>\r
 HARDWARE: Athlon 1 GHz / 128Mb<br>\r
 SOFTWARE: Windows 2000 / ActivePerl 5.6<br>\r
 CONFIG OPTIONS: <a href="awstats_config.html#LogFormat">LogFormat</a>=1, <a href="awstats_config.html#DNSLookup">DNSLookup</a>=0<br>\r
 AVERAGE SPEED: <b>4100</b> lines by seconds<br>\r
 Other times for different kind of web sites are shown lower in this page...<br>\r
+\r
+<br>\r
 <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 is about <b>1/120</b> of source log file(s).<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
+\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
@@ -58,8 +69,10 @@ So, have a look at the following chart to:<br>
 - Get more real ideas on benchmarks results<br>\r
 - Get more information and advice on a good setup for your site.<br>\r
 \r
+<br>\r
 <br>\r
 <b><u>This is examples of frequency/parameters you should use to have a good use of AWStats:</u></b><br>\r
+<br>\r
 <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>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></tr>\r
@@ -82,9 +95,10 @@ So, have a look at the following chart to:<br>
 ** Free memory required for update process (in MB). Warning: If you use the <a href="awstats_config.html#URLWithQuery">URLWithQuery</a> option, this value is doubled.<br>\r
 *** Duration is with Athlon 1GHz/128Mb and LogFormat=1.<br>\r
 \r
-\r
+<br>\r
 <br>\r
 <b><u>This is a summary of main ways to speed up AWStats:</u></b><br>\r
+<br>\r
 - You can disable <a href="awstats_config.html#DNSLookup">DNSLookup</a> in AWStats (set DNSLookup=0) but this requires\r
 that hosts addresses in your log file are already resolved (need to setup your\r
 web server to do so). Log analyze speed can be increased by 2 to 50 times but your web server will be slowed.<br>\r