From: eldy <>
Date: Sat, 8 Mar 2003 20:11:55 +0000 (+0000)
Subject: Updated documentation.
X-Git-Tag: AWSTATS_5_5_BETA~68
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bd8bb3d01c06a070faea6c342298c60352aa80ea;p=thirdparty%2FAWStats.git
Updated documentation.
---
diff --git a/docs/awstats_compare.html b/docs/awstats_compare.html
index 4b91923a..619f5da9 100644
--- a/docs/awstats_compare.html
+++ b/docs/awstats_compare.html
@@ -101,7 +101,7 @@
| Daily statistics | Yes | Yes | Yes | Yes |
| Monthly statistics | Yes | Yes | Yes | Yes |
| Yearly statistics | Yes | Yes | Yes | Yes |
-Benchmark with no DNS lookup in lines/seconds
(full features enabled, with XLF format, standard Perl 5.8, Athlon 1Ghz) | 4500**** | ?**** | 12000**** | NA
No program to run |
+Benchmark with no DNS lookup in lines/seconds
(full features enabled, with XLF format, standard Perl 5.8, Athlon 1Ghz) | 4500**** | 29000**** | 12000**** | NA
No program to run |
Benchmark with DNS lookup in lines/seconds
(full features enabled, with XLF format, standard Perl 5.8, Athlon 1Ghz) | 80**** | 80**** | 80**** | NA
No program to run |
| Graphical statistics in one page / several / or frames | Yes/Yes/Yes | Yes/No/No | Yes/Yes/No | No/Yes/Yes |
@@ -120,12 +120,15 @@ So, if you have only 2000 visits a month, products with no robot detection capab
Those rules are updated with AWStats updates.
But AWStats has also an algorithm to detect keywords of unknown search engines with unknown url syntax rules.
-**** As you can see, some log analyzers have, by default, very poor (or not at all) robots, search engines, os or
-browsers detection capabilities. So to have a benchmark comparison that means something, some log analyzers features
-were 'enhanced' with AWStats databases, when it was possible (For example, Webalizer config file was completed with
-this file. Like that, Webalizer features are a little bit closer than thoose of AWStats.
-Without this add (using default conf file), Webalizer results are 3 times faster but with less features).
-Benchmarks was made on a combined (XLF/CLF) log record on an Athlon 1GHz.
+**** Other log analyzers have poor (or not at all) robots, search engines, os or
+browsers detection capabilities and few features (no or poor visits count, bad filter rules, etc...).
+It is not possible to add all AWStats features to other log analyzers, so don't forget that benchmarks
+results are for 'different features' (for this benchmark, I did just complete Webalizer and Analog robots
+or search engines databases with part of AWStats database. So Webalizer config file was
+completed with this file, Analog config file was
+completed with this file.
+Note that without this very light add (using default conf file), Webalizer speed is 3 times faster, Analog is 15% faster).
+Benchmark was made on a combined (XLF/CLF) log record on an Athlon 1GHz.
You must keep in mind that all this times are without reverse DNS lookup. DNS lookup speed depends on your system, network and
Internet but not on the log analyzer you use. For this reason, DNS lookup is disabled in all log analyzer benchmarks.
Don't forget that DNS lookup is 95% (even with a lookup cache) of the time used by a log analyzer, so if your host is not