![]() |
AWStats logfile analyzer 5.9 Documentation |
| Your Web site traffic | Recommended values for parameters | Recommended update frequency (Rotate log delay) | Memory required** | Duration*** | ||
| DNSLookup* | URLWithQuery | URLReferrerWithQuery | ||||
| 0 - 1,000 visits/month | 1 | 0 or 1 | 0 or 1 | Once a day Log files are 0-1 MB 2000 lines to process | 4 MB free | 2mn |
| 0 (or 2) | 0 or 1 | 0 or 1 | Once a day Log files are 0-1 MB 2000 lines to process | 4 MB free | 1s | |
| 1,000 - 10,000 visits/month | 1 | 0 or 1 | 0 or 1 | Once a day Log files are 1-10 MB 2000-20000 lines | 4-8 MB free | 2-10mn |
| 0 (or 2) | 0 or 1 | 0 or 1 | Once a day Log files are 1-10 MB 2000-20000 lines | 4-8 MB free | 1-10s | |
| 10,000 - 100,000 visits/month | 1 | 0 or 1 | 0 or 1 | Every 12 hours Log files are 5-50 MB 10000-100000 lines | 8-16 MB free | 5-50mn |
| 0 (or 2) | 0 or 1 | 0 or 1 | Every 12 hours Log Files are 5-50 MB 10000-100000 lines | 8-16 MB free | 5-50s | |
| 100,000 - 500,000 visits/month | 1 | 0 | 0 or 1 | Every hour Log Files are 4-16 MB 10000-50000 lines | 16-64 MB free | 5-25mn |
| 0 (or 2) | 0 | 0 or 1 | Every hour Log Files are 4-16 MB 10000-50000 lines | 16-64 MB free | 5-25s | |
| 500,000 - 2,000,000 visits/month | 0 (or 2) | 0 | 0 | Every hour Log Files are 16-64 MB 50000-200000 lines | 64-256 MB free | 25-120s |
| 2,000,000 - 4,000,000 visits/month | 0 (or 2) | 0 | 0 | Every hour Log Files are 64-128 MB 200000-400000 lines | 256-512 MB free | 120-240s |
| +4,000,000 visits/month | AWStats is not a good choice for such web sites. Try a tool with less features but faster like "row counter log analyzers" like Analog (Can try also Webalizer) | |||||



- Check that DNSLookup is disabled in AWStats (DNSLookup must
be set to 0, or 2 to only use a DNS file resolver). Note that you still can have a 'Country' report
without DNS lookup enabled. For this you must enable the 'geoip' plugin. Without this plugin, 'Country'
report will works only if hosts addresses in your log file are already resolved (need to setup your web
server to do so, your web server will be slowed). With DNSLookup enabled, log analyze speed is decreased
by 40 to 100 times.


- Use carefully parameters URLWithQuery, URLReferrerWithQuery and URLWithAnchor
(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 URLQuerySeparators.
If you really need to use URLWithQuery=1, check that URLWithQueryWithoutFollowingParameters is set properly.


- 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).

- Use last Perl version (For example 5.8 is 5% faster than 5.6) and, more important, use standard Perl distribution instead of ActiveState (For example Standard Perl 5.8 Win32 binary is 25% faster than
ActiveState. And ActiveState 5.006, and may be other versions, have important memory problems making speed of analysis slower and slower when analysing more and more lines).
- Use last AWStats version.
- If you use Apache and don't rotate your logs (not the best way of working), set PurgeLogFile to 1 (By default, to avoid bad surprise,
PurgeLogFile is 0 in configure file, but you can set it to 1 to ask AWStats
to purge the log file after processing it, this increase speed for next run).