Logging Page Execution Time in ASP: Part 1
By: Danilo Celic on Thursday, May 26, 2005
Reader Level: 
As you're developing your applications, you may find that some pages are running slower than you'd expect them to (or rather you're getting frantic emails and voice mails from your client about pages running slow). Before you start running to refactor the coding of the page by recoding stored procedures and adding fancy caching mechanisms, you should first determine where the bottlenecks are in the application. Only after that will you know where to focus your efforts to get the most bang for the buck. For example, with a report that is only run once a quarter by your CFO, shaving a second off the rendering time of the report may not be the best use of your time (in your eyes anyway, don't ask the CFO) especially when compared to shaving a half-second of processing time off of pages that are run hundreds of times, if not thousands of times a day by your site visitors.
This article series will describe how to time the work your pages are performing to determine where your bottlenecks are located. This part of the series will use ASP VBScript to write out a log of timed activity to a CSV file so that you can process the results in Excel, Access, or some other analysis application. Example files are included in the support files for this article.
Purchase this item
You can purchase this piece of content separately for
$3.00
Want more?
Community MX members get unlimited access to daily articles,
tutorials, extensions and support. The most comprehensive
resource for Macromedia designers and developers today.
Take a tour of what we offer, and discover the benefits
of subscribing.
Already a member?
Simply log in using the form in the top right area of the site.
