I want to conduct a stress and performance test on the front-end of my ASP.NET app. My goal is to:
我想在我的ASP前端进行一次压力和性能测试。我的目标是:
- Identify bottlenecks
- 识别瓶颈
- Learn the number and the load of HTTP requests
- 了解HTTP请求的数量和负载
- Easily determine the components that are using an Expires header and/or being gzipped
- 很容易地确定使用过期头和/或gziked的组件
- Figure out where to increase download parllelization
- 弄清楚哪里可以增加下载的使用范围
- Locate duplicate scripts and unncessary redirects
- 找到重复的脚本并重定向
- Determine the load that will bring down the servers
- 确定将导致服务器宕机的负载
- Pinpoint key areas of server optimization
- 确定服务器优化的关键领域
Besides YSlow and Fiddler, are there any other tools that I should use to complete this test? Also, please share any best pratices for conducing this kind of test with me.
除了YSlow和Fiddler，还有什么其他工具可以让我完成这个测试吗?同时，请与我分享进行这种测试的最好的方法。
Thanks for your help,
John
谢谢你的帮助，约翰。
2 个解决方案
#1
2
Visual Studio Test Edition (2008/10) is a great tool for the job. You create individual web tests and combine the to generate a load on your webserver.
Visual Studio测试版(2008/10)是一个很好的工具。您可以创建单独的web测试，并将它们组合在web服务器上生成负载。
•Identify bottlenecks The tool allows you to configure exactly the perfmon stats you want to analyse. 2010 also automates the process of taking a database trace.
•识别瓶颈这个工具可以让你精确地配置你想要分析的性能数据。2010年还自动化了获取数据库跟踪的过程。
•Learn the number and the load of HTTP requests This requires some analysis of your IIS logs. Get a copy of Logparse2.2 (free MS tool). Load the logs into a database and have a look at what is going on.
•了解HTTP请求的数量和负载，这需要对IIS日志进行一些分析。获取Logparse2.2(免费的MS工具)的副本。将日志加载到数据库中，并查看发生了什么。
•Easily determine the components that are using an Expires header and/or being gzipped Again the IIS logs are the best place to get a handle on what is there.
•轻松确定使用过期头和/或被gzip压缩的组件，IIS日志是处理现有内容的最佳位置。
•Figure out where to increase download parllelization The IIS logs will tell you where abouts your actual users are hitting things, but Chrome has a really nice tool to investigate page by page the timing of invidual items.
•弄清楚在哪里增加下载的权限，IIS日志会告诉你你的实际用户在哪里点击东西，但是Chrome有一个很好的工具，可以一页一页地研究每个条目的时间。
•Locate duplicate scripts and unncessary redirects Not sure for this.
•查找重复的脚本并重定向不确定。
•Determine the load that will bring down the servers Create a load test based on a "common" group of pages requests from the live site. Add virtual users until the site dies. Be aware that any half decent webserver is going to require quite a bit of processing to take down, so you will require a licence for the MS load agents in order to generate enough load. Visual Studio 2010 will allow you to buy a licence for a number of virtual users and spread the virtual users of a number of machines in order to get a good load happening.
•确定将导致服务器宕机的负载，根据来自live站点的“常见”页面请求组创建负载测试。添加虚拟用户，直到站点死亡。请注意，任何一个优秀的webserver都需要大量的处理，因此您将需要MS负载代理的许可证才能生成足够的负载。Visual Studio 2010将允许您为许多虚拟用户购买一个许可证，并将许多机器的虚拟用户传播出去，以获得良好的负载。
•Pinpoint key areas of server optimization The load test tool captures the server perfmon statistics and allows you to find out the server bottlenecks. The test also capture the response times for individual pages, identifying particularly slow pages for improvement.
•定位服务器优化的关键领域负载测试工具捕获服务器性能统计数据并允许您查找服务器瓶颈。该测试还捕获单个页面的响应时间，识别出特别慢的页面以进行改进。
#2
0
If you have the money Web Metrics has an interesting offering called SiteStress (http://www.webmetrics.com/products/site_stress.html). I looked into them a year or so ago but didn't end up using them.
如果您有钱，Web Metrics有一个有趣的产品叫做SiteStress (http://www.webmetrics.com/products/site_stress.html)。我大约一年前研究过它们，但最终没有使用它们。
#1
2
Visual Studio Test Edition (2008/10) is a great tool for the job. You create individual web tests and combine the to generate a load on your webserver.
Visual Studio测试版(2008/10)是一个很好的工具。您可以创建单独的web测试，并将它们组合在web服务器上生成负载。
•Identify bottlenecks The tool allows you to configure exactly the perfmon stats you want to analyse. 2010 also automates the process of taking a database trace.
•识别瓶颈这个工具可以让你精确地配置你想要分析的性能数据。2010年还自动化了获取数据库跟踪的过程。
•Learn the number and the load of HTTP requests This requires some analysis of your IIS logs. Get a copy of Logparse2.2 (free MS tool). Load the logs into a database and have a look at what is going on.
•了解HTTP请求的数量和负载，这需要对IIS日志进行一些分析。获取Logparse2.2(免费的MS工具)的副本。将日志加载到数据库中，并查看发生了什么。
•Easily determine the components that are using an Expires header and/or being gzipped Again the IIS logs are the best place to get a handle on what is there.
•轻松确定使用过期头和/或被gzip压缩的组件，IIS日志是处理现有内容的最佳位置。
•Figure out where to increase download parllelization The IIS logs will tell you where abouts your actual users are hitting things, but Chrome has a really nice tool to investigate page by page the timing of invidual items.
•弄清楚在哪里增加下载的权限，IIS日志会告诉你你的实际用户在哪里点击东西，但是Chrome有一个很好的工具，可以一页一页地研究每个条目的时间。
•Locate duplicate scripts and unncessary redirects Not sure for this.
•查找重复的脚本并重定向不确定。
•Determine the load that will bring down the servers Create a load test based on a "common" group of pages requests from the live site. Add virtual users until the site dies. Be aware that any half decent webserver is going to require quite a bit of processing to take down, so you will require a licence for the MS load agents in order to generate enough load. Visual Studio 2010 will allow you to buy a licence for a number of virtual users and spread the virtual users of a number of machines in order to get a good load happening.
•确定将导致服务器宕机的负载，根据来自live站点的“常见”页面请求组创建负载测试。添加虚拟用户，直到站点死亡。请注意，任何一个优秀的webserver都需要大量的处理，因此您将需要MS负载代理的许可证才能生成足够的负载。Visual Studio 2010将允许您为许多虚拟用户购买一个许可证，并将许多机器的虚拟用户传播出去，以获得良好的负载。
•Pinpoint key areas of server optimization The load test tool captures the server perfmon statistics and allows you to find out the server bottlenecks. The test also capture the response times for individual pages, identifying particularly slow pages for improvement.
•定位服务器优化的关键领域负载测试工具捕获服务器性能统计数据并允许您查找服务器瓶颈。该测试还捕获单个页面的响应时间，识别出特别慢的页面以进行改进。
#2
0
If you have the money Web Metrics has an interesting offering called SiteStress (http://www.webmetrics.com/products/site_stress.html). I looked into them a year or so ago but didn't end up using them.
如果您有钱，Web Metrics有一个有趣的产品叫做SiteStress (http://www.webmetrics.com/products/site_stress.html)。我大约一年前研究过它们，但最终没有使用它们。