blocks|key|1543710|text|你最好的bet...as我已经说过上百万次了，before...is+Red+Gate工具集。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1543711|ANTS+Performance+Profiler是为您准备的工具。|1543712|对于SQL分析，您始终可以使用SQL+Server附带的内置事件探查器。|1543713|entityMap|0|LINK|mutability|MUTABLE|url|http://www.red-gate.com/|1|http://www.red-gate.com/products/ants_performance_profiler/index.htm^0|Z|8|0|0|0|P|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

Your best bet...as I've said a million times before...is the <a href="http://www.red-gate.com/" rel="nofollow noreferrer">Red Gate</a> set of tools.

<a href="http://www.red-gate.com/products/ants_performance_profiler/index.htm" rel="nofollow noreferrer">ANTS Performance Profiler</a> is the tool for you.

For SQL Profiling, you can always use the built in Profiler that comes with SQL Server.

blocks|key|1543726|text|如果您只需要这样做一次，或者您没有足够的钱来购买您可能找到的分析器，那么您总是可以求助于跟踪。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1543727|在从web服务或数据库调用中拉回结果的C#代码中，用代码包装调用，以检测调用需要多长时间。将其写入某个日志文件、调试输出或直接写入结果页。对其他看起来可疑的情况做类似的事情。|1543728|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you only need to do this once, or you don't have enough money for whatever profilers you may find, you can always resort to tracing.

In the C# code that pulls back results from a web service or database call, wrap the call with code to detect how long the call takes. Write that to some log file, debug output, or straight into the resulting page. Do similar things for other situations that appear suspicious.

blocks|key|1356933|text|系统是否只在一个环境中表现不佳，即数据集比您开发的数据集更大？这对我们来说一直是个问题，在过去，b/c人们会对小数据集编写糟糕的查询，但直到我们投入生产时才会注意到这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1356934|如果不是，我相信人们会推荐很多好的工具，比如SQL+Profiler，Visual+Studio的Profiler，或者在你的ASP页面上简单地使用Trace=true。对于AJAX，我发现像Firebug这样的JavaScript调试器对于查看幕后发生的事情很有用。|1356935|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Does the system only behave poorly in one environment, i.e. with a larger dataset than what you develop against? That has been a problem for us a lot in the past b/c people will write bad queries against small sets of data but never notice until we hit production. 

If not then I'm sure folks will recommend lots of good tools such as SQL Profiler, Visual Studio's Profiler, or simply using Trace=true on your ASP .Net pages. For AJAX I find a JavaScript debugger like Firebug useful for seeing what's going on behind the scenes.

blocks|key|1543751|text|Jetbrains有一款名为dotTrace的产品，它可以监控性能和内存。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1543752|entityMap|0|LINK|mutability|MUTABLE|url|http://www.jetbrains.com/profiler/^0|E|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Jetbrains has a product called <a href="http://www.jetbrains.com/profiler/" rel="nofollow noreferrer">dotTrace</a> which monitors performance as well as memory.

blocks|key|241819|text|可能最好的第一步是确定花费时间的是数据库还是前端。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|241820|Red+Gate工具也很有用，尽管如果您不确定它们告诉您要修复的是什么，您可能希望从更基本的级别开始。如果是数据库，那么SQL+Server事件探查器就是您的朋友。这里有一些基本的痕迹，特别注意持续时间和阅读，这将为你指明正确的方向，或者至少帮助你确定问题所在。|241821|在web端，跟踪标志可能特别有用。|241822|祝好运!丹|241823|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Probably the best first step is to determine whether it is the database that is taking the time or the front end. 

Red Gate tools can also be useful, although if you're not sure what they're telling you to fix, you may want to start at a more basic level. If it's the database, then SQL Server profiler is your friend. A few basic traces in there, paying particular attention to duration and reads will point you in the right direction, or at least help you identify the problem areas.

On the web side, the trace flags can be particularly useful.

Good luck!
Dan

blocks|key|242166|text|Google+Page+Speed+--一个Firebug插件--也可以用来跟踪加载ASPX页面时消耗你的时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|242167|顺便说一句，通常一个巨大的ViewState也可能是Aspx页面上的一个问题。|242168|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/speed/page-speed/|1|http://getfirebug.com/^0|0|H|0|M|7|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

<a href="http://code.google.com/speed/page-speed/" rel="nofollow noreferrer">Google Page Speed</a> - a <a href="http://getfirebug.com/" rel="nofollow noreferrer">Firebug</a> plugin - may also be an option to trace what consumes your time when loading the ASPX pages.

Btw, often also a huge ViewState may be an issue on Aspx pages.

blocks|key|242178|text|关于@Juri所说的更多，也可以获得Firebug的YSlow插件。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|242179|我首先要做的几件事是解决速度问题：|242180|242181|将所有CSS文件合并为一个(并将所有Javascript文件合并为一个(并缩小)|ordered-list-item|242182|页面上有多少个图像？考虑使用Sprite.|242183|页面上的任何404？|242184|242185|另外，您是否尝试使用Trace="true“。|242186|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.yahoo.com/yslow/^0|Q|5|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|13|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|14|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|15|8|@]|9|@]|C|$]]|$1|L|3|M|5|I|7|16|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|17|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

More on what @Juri said, also get the <a href="http://developer.yahoo.com/yslow/" rel="nofollow noreferrer">YSlow</a> plugin for Firebug.

A few things I go to first to fix speed:

<ol>
<li>Combine all CSS files into one (and minify)</li>
<li>Combine all Javascript files into one (and minify)</li>
<li>How many images do you have on the page? Consider using Sprites.</li>
<li>Any 404s on the page?</li>
</ol>

Also, did you try just using Trace="true".

We have MSSQL, some C# web services, some ASP.NET, and some AJAX. We're having terrible load times, normally 2-3 seconds to refresh a page, sometimes far more. I have no idea where to start.

What profiling tools are there, across the entire end-to-end, to identify where the biggest bottlenecks are?

finding performance bottlenecks in ASP.NET

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们有MSSQL、一些C# web服务、一些ASP.NET和一些AJAX。我们有可怕的加载时间，通常2-3秒刷新一个页面，有时甚至更多。我不知道从哪里开始。在整个端到端过程中，有哪些分析工具可以确定最大的瓶颈在哪里？

问查找ASP.NET中的性能瓶颈
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问查找ASP.NET中的性能瓶颈EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问查找ASP.NET中的性能瓶颈
EN