Click here to Skip to main content
15,882,055 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I have a very strange problem. I have a webapplication that runned very smoothly. Last week I moved the webapplication from a server with Windows 2012 en SQL Server 2016, to a new server with Windows 2019 and SQL Server 2019. The new server has more CPU's, more memory.

But when I open my site and try to save changes, it's unacceptably slow. It can take minutes to save. The problem is not the database, I've checked that. Running the same locally on my dev-PC, no problem.

Now I've added the following to my web.config to trace and try to figure out the problem. And that's the strange thing. With this it runs at normal speed.

<trace pageOutput="false" requestLimit="10" enabled="true" localOnly="true" traceMode="SortByTime" mostRecent="true"/>

How can this be? I don't want trace to be enabled for security reasons. But when I remove it, my webapp is slow again.

Anyone any answers?


What I have tried:

Made sure the cause of the problem wasn't the database. I compared the web.config with the old situation, where it was running fine, to see if there are any discrepencies, but there aren't. Apart for a rewrite that I removed, it's exactly the same. Adding the rewrite back didn't help either.
Posted
Comments
Richard Deeming 10-Mar-20 8:48am    
Is tracing enabled at the server level? I don't think there's a specific UI for it, but you should be able to check using the "Configuration Editor" in IIS Manager.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900