 |
 |
 |
 |
|
 |
 |
on the size of the reporting database, the type of report requested, the speed of
the server and the speed of the end user’s connection to the server.
Here are some suggestions that can help improve the parsing and reporting
performance.
1.
If the page views for a site profile exceeds 20 million page views for the
complete period (even on a reasonably fast server) use a site profile per
specific period. For instance you can set up four site profile for the four
quarters of the year instead of having one profile that spans the whole
year.
2.
Rotate log files daily and not hourly. The MergeClient process has to check
every file in the log source directory for changes and hourly log file
rotation would require more log files to check resulting in slower
performance. It is also more difficult to specify and manage.
3.
Generate log files per web site and not one containing multiple websites’
log entries.
4.
Use a dedicated reporting server if your web servers are busy.
5.
Remove old data from the reporting database of profiles.
6.
Use filters to parse only relevant data to the database and do not add hits
to images to the database.
7.
Get a faster processor, more memory and make sure you have enough
disk space.
8.
Move out or zip already processed log files from the source log file
directory.
9.
Use JavaScript in web pages on very busy web sites to generate log file
entries. This creates smaller and less complex log files.
Administration Guide
This guide is intended to help explain the concepts and operational issues of
administering the SurfStatsLive Reporting Service. Please read this section
carefully to understand the concepts presented before installing the software on
the server.