简体繁体 English

从.NET 1.1迁移到.NET 4.0后的几个性能问题

[英]Several Performance Issues after migrating from .NET 1.1 to .NET 4.0

原文 2014-03-07 02:39:31 2 1 c#/ asp.net/ .net/ vb6

We migrated an ASP.NET 1.1 web application to 4.0 and since then the performance has been getting worse day by day. 我们将ASP.NET 1.1 Web应用程序迁移到4.0，从那时起，性能就变得越来越差。 Pages take about 5-6 minutes to load, even a simple one. 加载页面大约需要5-6分钟，甚至很简单。 Classic ASP goes fast as the wind, but ASPX.. oh my. 经典ASP随风而行，但是ASPX ..哦，我的。 Yesterday I let Debug Diagnostics running an analysis on the machine and will see it tomorrow. 昨天，我让Debug Diagnostics在计算机上运行分析，明天将看到它。 Besides, I searched for similar problems and found these 2 threads with possible solutions -- we use lots of VB6 dlls as unmanaged code to do all sort of stuff. 此外，我搜索了类似的问题，并找到了可能的解决方案这2个线程-我们使用许多VB6 dll作为非托管代码来完成各种工作。 Could they be the problem? 难道是问题吗？ What do you guys think? 你们有什么感想？ In the second link, the question author answered that he found the problem - it was a recordsetclass update method that was making performance go down. 在第二个链接中，问题作者回答说他发现了问题-这是一个记录集类更新方法，导致性能下降。

Any ideas? 有任何想法吗？

Unexpected behaviour after migrating from .NET 1.1 to 3.5 从.NET 1.1迁移到3.5后的意外行为

Performance issues after upgrading from asp.net 1.1 to 3.5 从asp.net 1.1升级到3.5后的性能问题

1 个解决方案

Just found out what was happening, is case anyone wants to know. 刚发现发生了什么，就是任何人想知道的情况。 There was a call to Environment.Stacktrace (the getter method) that was hanging heavily, besides being called at every database access (wow) -- almost 100% of IIS threads were blocked by this call. 除了在每次访问数据库时都被调用外，对Environment.Stacktrace（getter方法）的调用已被大量挂起（哇）-几乎100％的IIS线程都被该调用阻塞了。 Not sure the reason, but this call used to work fine in .NET 1.1 and I couldn't find any clues about it. 不知道原因，但是此调用过去在.NET 1.1中正常工作，我找不到任何线索。

btw, sorry about saying 'thanks', I'm new around here, it was my first question - won't happen again. 顺便说一句，很抱歉说“谢谢”，我是这里的新手，这是我的第一个问题-不会再发生了。