Chapter 17Analyzing and Boosting PerformanceIn This Chapter Learning why you should monitor, boost, and forecast Windows 2000 Server performance Defining performance analysis Learning about and distinguishing between quantitative and qualitative tools Learning the conceptual steps in performance analysis Learning about troubleshooting via performance analysis Knowing what the four most important areas to monitor in order to boostperformance are Reasons for declines in performanceAnalyzing and boosting performance is a very important part of a Windows2000 Server professional’s job. You are responsible for getting the mostfrom your implementation of Windows 2000 Server. Installing, managing, andusing Windows 2000 Server is a big investment on your part in both time andmoney. By analyzing and boosting performance, you can increase the return onthat investment. This chapter will not only define performance analysis fromboth quantitative and qualitative viewpoints, but will also set the foundationfor the chapters that follow in Part VI, “Optimizing Windows 2000 Server.”This chapter is for the MBA in all of us. While MBAs spend their days applyinglinear programming to business scenarios and mastering the inner workingsof their Hewlett-Packard (HP) 12C calculators, Window 2000 Server engineerscan learn a lot from the basics of quantitative analysis used by MBAs. You can apply the quantitative or scientific approach to Windows 2000 Serverperformance analysis and add real value to your network and its operations.To do so, consider mastering System Performance Monitor, Network Monitor,and Task Manager.Why? Smart practitioners know that you get what you give to Windows 2000Server. If all you do is set up and simply answer several questions posed bythe Windows 2000 Server setup dialog boxes, your signature will be on publicdisplay when others follow and look closely at your network. Simple is as4620-1 ch17.f.qc 10/28/99 12:19 PM Page 541simple does. A network setup in a simple fashion will basically perform, but doom lurks. Once your network experiences significant growth either via user count or activity levels, system design and implementation issues often return to wreak havoc. Thus the need to study, master, and implementthe performance boosting secrets discussed in this and the next few chaptersin the Performance Analysis part. These secrets include third-party productsthat add to and help you exceed the capabilities of Microsoft’s built-inperformance analysis tools.Performance AnalysisWe wouldn’t embark on a sailing trip without a plan, a map, and a compass in our stash of necessities. We like to know where we are headed, how long it will take, and often, whether we can get there sooner. ManagingWindows 2000 Server environments is no different. Is our Windows 2000Server performance headed in the right direction? Going south on us?Remaining stable or veering sideways? These are the types of questions we ask ourselves in the middle of the night, workaholics that we are in this exciting and demanding field of Windows 2000 Server networkadministration and engineering. To answer these questions, wetinker, try again, and tinker more, hoping to boost Windows 2000 Server performance and predict where our environment is headed.Chant the following mantra: It all starts with the data. While this is a popularrefrain among database administrators (DBAs), it is the data that ultimatelymatters when analyzing and boosting the performance of Windows 2000Server-based networks. Data is at the center of our efforts to analyzeWindows 2000 Server, so we place great importance on the type of data, the quantity of data, and the quality of data we can obtain from Windows2000 Server. Fortunately, the computer readily generates this data for us. Thank God we don’t have to record by hand like the door-to-door U.S. government census interviewers of days gone by.Data can be collected as a one-time snapshot of our system health, or it canbe systematically collected over time. As quantitative analysts, we desire andseek out large clean data sets that provide enough values for us to performmeaningful analysis and draw meaningful conclusions.Whichever data analysis tool you use to monitor and manage your Windows2000 Server network, you should strive to collect data consistently, frequently,and routinely. We love large data sets as the foundation of our analysis.Statistically, we refer to a large data set as a large sample size.542 Part VI: Optimizing Windows 2000 Server■ ■4620-1 ch17.f.qc 10/28/99 12:19 PM Page 542Built-in performance analysis toolsIn Windows 2000 Server, we typically use six tools to collect and analyze our data: System Performance Monitor, Network Monitor, Task Manager,Windows 2000 System Information, Event Viewer, and Device Manager.System Performance Monitor enables us to perform sophisticated analysisvia charts, logs, reports, and alerts over time (see Figure 17-1). SystemPerformance Monitor is discussed at length in Chapter 18. Network Monitoris truly a gift in Windows 2000 Server, enabling basic networking packetanalysis without having to spend $5,000 or more on a hardware-based sniffer (see Figure 17-2). Network Monitor is discussed at length in Chapter 19. Task Manager (see Figure 17-3), Windows 2000 SystemInformation (see Figure 17-4) and Event Viewer (see Figure 17-5) arediscussed extensively in Chapter 20. You can also read more about System Performance Monitor, Network Monitor, and Task Manager in the “Are You Being ‘Outperformed?’” section of this chapter. DeviceManager, a welcome addition to the Windows 2000 family, was discussed in Chapter 9 (see Figure 17-6).Figure 17-1: Default view of System Performance Monitor showing the Object:ProcessorCounter:% Processor TimeChapter 17: Analyzing and Boosting Performance 543■ ■4620-1 ch17.f.qc 10/28/99 12:19 PM Page 543Figure 17-2: Default view of Network Monitor—Capture View windowFigure 17-3: Default view of Task Manager—Performance tab sheet544 Part VI: Optimizing Windows 2000 Server■ ■4620-1 ch17.f.qc 10/28/99 12:19 PM Page 544Figure 17-4: Default view of Windows 2000 System Information—System SummaryFigure 17-5: Default view of Event Viewer—System LogChapter 17: Analyzing and Boosting Performance 545■ ■4620-1 ch17.f.qc 10/28/99 12:19 PM Page 545Figure 17-6: Default view of Device ManagerEach of these tools, except for Device Manager (already discussed in