Menu
I have a classic ASP (JScript) web-site that is running slow and are there any profilers that can help me identify what is taking time?
Other hints on how to optimize or debug ASP performance issues would be helpful.
800
Classic ASP is a server-side scripting environment that you can use to create and run dynamic web applications. With ASP, you can combine HTML pages, script commands, and COM components to create interactive web pages that are easy to develop and modify.
Classic ASP uses server-side scripting to dynamically produce web pages that are not affected by the type of browser the website visitor is using. The default scripting language used for writing ASP is VBScript, although you can use other scripting languages like JScript (Microsoft's version of JavaScript).
In Visual Studio 2015, click File –> New –> Project…, then in the new project dialog, search “ASP.NET Web Application”. A WebApplication.
In the remote debugging tool select tools-> options -> no authentication for all users. Go to visual studio and attach to process w3wp.exe. if cant see the process (w3wp.exe). Open the website link in browser and select show for all users now u will be able to see the process and attach.
Assuming you're looking for free solutions, here are some suggestions used in past (very old) project of mine:
ASP Profiler component. This is a line-level performance profiler for Active Server Pages (with VBScript) code. It shows how your ASP page runs, which lines are executed how many times, and how many milliseconds each take. Especially for heavy data-driven pages, you can see exactly which lines slow down the page, and optimize where necessary.
Googling around I have also found a couple of very old articles on timing/profiling ASP execution code: have a look here and here.
If you have an issue with server side code being slow I have found it is almost always the database causing the issue. You need to check for SQL which is slow to return a result; if you find any you need to look at applying new indexes to your tables. If your app is too chatty with the database you need to look at reducing the number of calls to the database. To find these problems you can always use SQL Server Profiler; this comes bundled with SQL Server 2005/2008 Developer edition.
Also you can use a free SQL Profiler available at xsqlsoftware.com
101
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
