I am setting up windows performance monitor to log activity on a web server while running MS Web application stress tool. Which counters should I choose to give me the best picture of where I have bottlenecks, slow performance and response etc?
我正在设置Windows性能监视器,以便在运行MS Web应用程序压力工具时记录Web服务器上的活动。我应该选择哪些计数器给我最好的图片,说明我的瓶颈,性能和响应速度等等?
cheers
1 个解决方案
#1
The windows performance tool, perfmon, is probably not going to tell you a lot about where your bottlenecks are, but it can help you determine the impact of the load you are putting on the system and if run long enough, is likely to tell you if you have resource leaks.
Windows性能工具perfmon可能不会告诉你很多关于你的瓶颈的地方,但它可以帮助你确定你对系统负载的影响,如果运行时间足够长,可能会告诉你如果你有资源泄漏。
My baseline items: All Process items for the process Processor Memory
我的基准项:进程处理器内存的所有进程项
For sampling period, I tend to target 100-200 samples for the length of the expected run.
对于采样周期,我倾向于将100-200个样本作为预期运行的长度。
The next set of questions will be very specific to your application to determine what you need: .Net and ASP objects if they apply Network objects if you suspect problems on the network interface Disk IO if you suspect or want to investigate impact how much disk activity is going on at different loads.
下一组问题将非常具体到您的应用程序,以确定您需要:.Net和ASP对象,如果他们应用网络对象如果您怀疑网络接口上的问题磁盘IO,如果您怀疑或想要调查影响磁盘活动多少正在进行不同的负载。
As important as collecting the data is the time to review. For first time views, it's worth taking an hour or two just to bring up each counter and notice the trends. Once you've become more experienced with the counters you can focus in on specific items. Things I tend to always review for leaks: handle counts, threads, private memory, free system page table entries, data base connection counts if you can get them.
收集数据同样重要的是审查时间。对于第一次观看,只需要花一两个小时来提出每个柜台并注意趋势。一旦您对计数器变得更有经验,您就可以专注于特定项目。我倾向于总是检查泄漏的事情:处理计数,线程,私有内存,免费系统页表条目,数据库连接计数,如果你可以得到它们。
Don't forget to look at the whole system and not just your web server. Application issues can show up on any of the linked (directly or indirectly) resources. Just because something else fails or is slow doesn't mean it wasn't caused by your application.
不要忘记查看整个系统,而不仅仅是您的Web服务器。应用程序问题可以显示在任何链接(直接或间接)资源上。仅仅因为其他东西失败或缓慢并不意味着它不是由您的应用程序引起的。
#1
The windows performance tool, perfmon, is probably not going to tell you a lot about where your bottlenecks are, but it can help you determine the impact of the load you are putting on the system and if run long enough, is likely to tell you if you have resource leaks.
Windows性能工具perfmon可能不会告诉你很多关于你的瓶颈的地方,但它可以帮助你确定你对系统负载的影响,如果运行时间足够长,可能会告诉你如果你有资源泄漏。
My baseline items: All Process items for the process Processor Memory
我的基准项:进程处理器内存的所有进程项
For sampling period, I tend to target 100-200 samples for the length of the expected run.
对于采样周期,我倾向于将100-200个样本作为预期运行的长度。
The next set of questions will be very specific to your application to determine what you need: .Net and ASP objects if they apply Network objects if you suspect problems on the network interface Disk IO if you suspect or want to investigate impact how much disk activity is going on at different loads.
下一组问题将非常具体到您的应用程序,以确定您需要:.Net和ASP对象,如果他们应用网络对象如果您怀疑网络接口上的问题磁盘IO,如果您怀疑或想要调查影响磁盘活动多少正在进行不同的负载。
As important as collecting the data is the time to review. For first time views, it's worth taking an hour or two just to bring up each counter and notice the trends. Once you've become more experienced with the counters you can focus in on specific items. Things I tend to always review for leaks: handle counts, threads, private memory, free system page table entries, data base connection counts if you can get them.
收集数据同样重要的是审查时间。对于第一次观看,只需要花一两个小时来提出每个柜台并注意趋势。一旦您对计数器变得更有经验,您就可以专注于特定项目。我倾向于总是检查泄漏的事情:处理计数,线程,私有内存,免费系统页表条目,数据库连接计数,如果你可以得到它们。
Don't forget to look at the whole system and not just your web server. Application issues can show up on any of the linked (directly or indirectly) resources. Just because something else fails or is slow doesn't mean it wasn't caused by your application.
不要忘记查看整个系统,而不仅仅是您的Web服务器。应用程序问题可以显示在任何链接(直接或间接)资源上。仅仅因为其他东西失败或缓慢并不意味着它不是由您的应用程序引起的。