RSS
|
||
  Log-Analysis Tools: Site Server Is on the Right Track | ||
|
|
Analyzing the Logs: How We Tested We tested all products on a Dell Computer Corp. Optiplex Pentium II running at 300 MHz with 256 MB of RAM under the Windows NT Server 4.0 operating system. All logs were imported into Microsoft Corp.'s SQL Server 6.5 database.
 The log files we tested ranged in size from 12 MB to a 1.2-GB proxy log (although none of the products could handle a file of this size). We obtained two of our log files from live corporate sites: one from a Fortune 100 company and another from a worldwide standards organization. For benchmark testing, we used a 100-MB log file that consisted of 111 million entries (more than 1 million hits)--a size indicative of what a large company might deal with if it were to rotate its log files on a daily basis. We tested each product under two performance benchmarks. In both performance tests, each product imported the 100-MB log file into the SQL database. The first time through, we asked each product to import the log file, but not to look up page titles or DNS lookups. (We called this our basic import.) After clearing all databases, we imported the log file again, this time performing title and DNS lookups. (This was our full import.)
Page title lookups require the software to contact the Web server and retrieve the page titles from the actual HTML pages. DNS lookups take each IP address and attempt to resolve the domain name. Although title and DNS lookups can yield valuable information, as you can see from the results of the two performance tests we conducted, it may take twice as long, or even longer, to run these imports. |
|
 |
||
|
Eight-Port Remote-Access Servers Provide Users With Solid Connectivity By Mike Fratto  Print This Page E-mail this URL |
||
