 |
 |
 |
 |
|
 |
 |
also added to the database and reported on. Some clients in the past (with the
SurfStats Log Analyzer product) reported that the database was empty when
there was only one 64 KB present and expected this information to be added to
the database. This is handled properly now, which means that log data written to
the last 64KB portion is reported on.
The default setting for ASP buffering is ON in IIS5/6. This causes the sc-bytes
field to be logged as 0. You should switch ASP buffering OFF to log this field. If
you do not do this, you will not be able to track bandwidth in reports on ASP files.
Log Time Period
In Internet Services Manager on the Extended Logging Properties screen (click
Properties on the Web Site tab for the Virtual Web Server.) you can set the Log
Time Period. The Log Time Period determines how frequently IIS will open up a
new log file. You can set any log time period, however it is recommended to use
the Daily option.
Please note that if you choose NOT to have the Log Time Period set to daily, the
SurfStatsLive automatic log file backup (which is set up in Server Administration)
will not work, meaning that the web server’s log files will not be moved to a
backup directory.
Performance Guidelines
Microsoft Windows pre-emptively multitasks processes running on the Operating
System. This means that the operating system determines the optimal processing
time slice to allocate to processes based on process requirements, process
priority and processing resources available. The SurfStatsLive MergeClient
process is the main workhorse in the collection of processes running on a server
with SurfStasLive installed. This process parses log files and updates the profile
reporting databases. It is started by SurfStatsLive and runs at a low priority. The
Operating System at times may decide to run the MergeClient process at 100%
CPU utilization if no other processes are requiring significant CPU processing
cycles. Other processes running at higher priority will get processing preference if
they require additional CPU cycles. You can verify this in the Windows Task
Manager (Processes tab) by looking at the percentage CPU allocation when the
MergeClient process is running and another process is started or requires
additional CPU processing cycles.
Log file parsing is a memory and CPU intensive operation and any log analyser
will choke on excessively large log files. Parsing performance depends on the size
and complexity of the log files, the set filters to include/exclude data and on the
speed of the server (CPU, memory and hard disk). The reporting speed depends