Analyzing and Optimizing Performance
上一篇 / 下一篇 2008-05-07 16:03:39 / 个人分类:LoadRunner
Analyzing and Optimizing Network Performance | ||
11.5.2 | Bottleneck |
A bottleneck is exactly what the name
implies. It is the point in the system that limits the data
throughput, which is the amount of data that can flow through the
network. A bottleneck can be caused by a problem with a component or by the inherent limitations of the component. An example might be a network that has 10/100-Mbps hubs and switches and computers with 10/100-Mbps network cards, but only Category 3 twisted-pair in the cabling infrastructure. Since Category 3 twisted-pair cable does not support a high data transfer rate, the cable is the bottleneck that slows down the network. It is doubtful that all network components can be fine-tuned so precisely that they all operate at exactly the same speed. Nonetheless, optimizing performance involves finding the bottlenecks and upgrading, reconfiguring, or replacing the components to bring their performance up to or above the level of the rest of the network components. This process almost inevitably creates a new bottleneck elsewhere, but with good planning the new bottleneck should be less restrictive than the old one. To be able to diagnose which network server component is causing a system bottleneck, there must be performance-monitoring software tools specific to the network server operating system. Most network server operating systems have at least a basic performance-monitoring software package included with the operating system. Third-party vendors also have performance-monitoring software tools available for most network server operating systems. Examples of performance-monitoring software tools for various network server operating systems include the following:
The primary performance-monitoring tool for Microsoft’s Windows 2000 Server is just called Performance, which is shown in Figure. Performance can monitor nearly all hardware and software components on a Windows 2000 server. The monitoring can take the form of creating a real-time chart of resource utilization, or it can take the form of a log file for later analysis. The log file can be analyzed or exported in a format that can be used by other software, such as a standard statistics software package for analysis or Microsoft Excel to generate charts or statistics. Windows 2000 Server Tool (Performance) is a snap-in to the Microsoft Management Console. The NT 4.0 performance monitor appearance is slightly different, but the basic functionality is almost identical. The various versions of the UNIX/Linux operating systems have command-line utilities that can be used to monitor performance of the UNIX/Linux network server. The primary tools aresar,vmstat,iostat, andps. The flags used by these commands can vary among the different versions of UNIX/Linux. Use the UNIX/Linuxmancommand to get specifics about the use of these commands. The information displayed by themancommand also tells how to interpret the output generated by the command. The UNIX/Linux System Activity Reporter, orsarcommand, collects and reports system activity, which includes processor utilization, buffer utilization, and so forth for the UNIX/Linux network server. The UNIX/Linux Virtual Memory Statistics, orvmstatcommand, provides information about the virtual memory system on the UNIX/Linux network server. The UNIX/Linux Input/Output Statistics, oriostatcommand, provides information about disk subsystem input/output on the UNIX/Linux network server. The UNIX/Linux Processes (ps) command lists all the processes that are running on the UNIX/Linux network server. Processor Bottlenecks
Memory Bottlenecks On network servers with operating systems that do support virtual memory, several indicators or counters should be monitored. The first counter is the amount of available memory, or memory that is not being used, after all the network server software has been loaded. To totally prevent paging or swapping of memory pages to the disk, just have more actual or physical memory than is needed by all the software running on the network server. The other counter that should be monitored to check for memory bottlenecks is the number of pages that are read from or written to the paging file on the disk in one second. The number of pages per second that is acceptable depends on the speed of the processor. Generally the number should be less than 2,000 per second. Heavy paging often manifests itself as high disk utilization, because the memory pages are written to the disk when the memory is needed by another program. Another indicator of lack of memory is the number of page faults generated per second. A page fault is the condition encountered when there is an attempt to access a program page, the page is no longer in memory, but it must be retrieved from the disk. A page fault problem is indicated if the number of page faults per second is more than double the number of page faults recorded on the server baseline measurements taken under a normal workload. To alleviate a memory bottleneck, add more memory to the network server. Paging performance can often be improved by placing the paging file, or the swap file, on the fastest disk in the network server. Also, this disk must not contain the network server operating system or the data files used by the major application running on the network server. Disk Subsystem Bottlenecks The disk subsystem counters that should be monitored are disk subsystem utilization and disk queue length. A disk subsystem utilization percentage should not be constantly greater than 90%. This very high disk subsystem utilization rate indicates that the disk subsystem is the bottleneck. The disk subsystem queue length indicates how many items are waiting to be written to the disk subsystem. A disk subsystem queue length that is constantly greater than two indicates that the disk sub-system is too slow. Several things might improve disk subsystem performance:
Network Subsystem Bottlenecks A network utilization percentage that is constantly greater than 65% is generally considered to be high utilization and can constitute a bottleneck. Solutions to a network subsystem bottleneck are generally expensive and include the following:
The following are a couple of well-known network monitoring and analysis tools:
|
来源:http://ca.htc.mnscu.edu/ne/custom_curriculum/Week14/11_5_2/content.html
相关阅读:
- LoadRunner 没有告诉你的(四) (shen1936, 2008-5-05)
- LoadRunner 没有告诉你的(五) (shen1936, 2008-5-05)
- LoadRunner没有告诉你的(六) (shen1936, 2008-5-05)
- lr监视的性能计数器 (fuqiuju, 2008-5-05)
- LoadRunner V8.0 安装问题求解 (jianfan13, 2008-5-06)
- LoadRunner的 227个问题 (51testing, 2008-5-06)
- 使用LoadRunner录制脚本时如何选择合适的协议?[转] (bingdu520, 2008-5-06)
- LoadRunner 虚拟IP操作步骤 (jely, 2008-5-06)
TAG: LoadRunner
标题搜索
日历
|
|||||||||
日 | 一 | 二 | 三 | 四 | 五 | 六 | |||
1 | 2 | ||||||||
3 | 4 | 5 | 6 | 7 | 8 | 9 | |||
10 | 11 | 12 | 13 | 14 | 15 | 16 | |||
17 | 18 | 19 | 20 | 21 | 22 | 23 | |||
24 | 25 | 26 | 27 | 28 | 29 | 30 |
我的存档
数据统计
- 访问量: 259852
- 日志数: 137
- 建立时间: 2007-08-14
- 更新时间: 2010-05-25