asked on
Classic ASP - troubleshoot poor performance
I have a classic ASP application running on a Windows 2008 R2 server, with a Microsoft Access backend. This is the only application running on the server.
Periodically, especially during busy times, the application will crawl to a halt. I have added more system resources to the server, but this is not resolved the issue. I have gone through the logs, including the failed requests, but it still unsure how to rectify.
Any thoughts on how to troubleshoot?
Periodically, especially during busy times, the application will crawl to a halt. I have added more system resources to the server, but this is not resolved the issue. I have gone through the logs, including the failed requests, but it still unsure how to rectify.
Any thoughts on how to troubleshoot?
ASPMicrosoft IIS Web ServerWeb ServersWeb DevelopmentVisual Basic Classic
Last Comment
cuadmin
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks for the advice - planning on moving the DB to MS SQL. Thanks guys!
Thanks for the reply. It’s a VM, hosted and supported by internal staff. Two 2.4 Ghz Xeon processors, 8 GB RAM on a 64-bit OS.
I have application transaction log that capture a variety of records – it’s anywhere from 1000-1500 on an average day to nearly 3000 on a busy day. (The log captures logins, logouts and saved records)
When it’s busy, or really slow, the login page will still load. It appears that when you run a query, during peak time, it kills the server or caused a long lag. Is there a way I can prove that it’s the database that’s killing the app?
I am running the performance monitor and, sometimes, I’ll see the ‘requests failed’ start to increase. Also, I am logging the FailedReqLogFiles – but ensure of what to make of these.
The Access DB is roughly 300 Mb. Would compacting a repairing the DB regularly help? I have one table that is about 70K records, another that is 66K, one that is around 10K and another that is around 4 K. Roughly 100 tables in all.
I am not allowing users to upload images.
Is there any other logging I should be doing? If it’s obvious that it’s the MS Access DB that’s causing the issue, what are my options? Could I move to MS Sql Express? Something else?
Thanks for your help!