性能问题升级从asp.net 1.1到3.5之后, [英] Performance issues after upgrading from asp.net 1.1 to 3.5

查看:153
本文介绍了性能问题升级从asp.net 1.1到3.5之后,的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有当把它升级到3.5 Asp.Net我们得到了该网站并没有进行投诉的Asp.Net 1.1目前运行的应用程序。
当我们看到了Web服务器的CPU的历史,然后我们可以看到,当网站上Asp.Net 1.1载荷为最大20%运行,并与3.5负荷约为40 - 60%

We have an application which currently runs on Asp.Net 1.1 When we upgraded it to Asp.Net 3.5 we got complaints that the web site was not performing. When we looked at the CPU history of the webservers then we see when the site was running on Asp.Net 1.1 the load was max 20%, and with 3.5 the load was around the 40 - 60%

我们的确发生了变化的唯一的事情就是Asp.Net升级,并在IIS 6中的设置和web.config中的变化。在code,我们没有改变任何东西。

The only thing we did change was the Asp.Net upgrade, and the settings in IIS 6 and the web.config change. In the code we did not change anything.

那么,什么是执行3.5好于1.1和不呢?
(服务器是2003的网络服务器)

So what is performing better in 1.1 and not in 3.5? (the server is an 2003 webserver)

推荐答案

我发现了问题是什么(以防万一有人想知道)。
我们在这里使用的是旧的DLL ADODB。和RecordSetClass.Update()所造成的问题。
在Asp.net 1.1它不是一个问题,但在2.0及更高它耗费了大量的CPU。

I found out what the problem was (just in case someone would like to know). We where using an old dll for ADODB. And the RecordSetClass.Update() was causing the problems. In Asp.net 1.1 its not a problem, but in 2.0 and later on its consuming a lots of cpu.

这篇关于性能问题升级从asp.net 1.1到3.5之后,的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆