1. Chapter 14 Chapter 14: Server Monitoring and Optimization

2. Chapter 14 Learning Objectives n Establish monitoring benchmarks n Monitor server services, logged-on users, and server functions n Use Task Manager to monitor processes and performance data n Use the System Monitor to monitor page file, memory, processor, disk and other critical server performance functions and to tune these functions as needed

3. Chapter 14 Learning Objectives (continued) n Set up performance logs and alerts for monitoring n Identify key system elements to monitor for problems

4. Chapter 14 Benefits of Server Monitoring n Monitoring helps you become familiar with normal server performance to help identify areas of growth, prevent problems, and troubleshoot problems later n Plan to monitor a range of activities to better understand a server

5. Chapter 14 Server Activities to Monitor Table 14-1 Server Activities to Monitor

6. Chapter 14 Establishing Server Benchmarks n Plan to establish server benchmarks as an effective way to determine normal performance and distinguish it from problem situations n Benchmarks can be established by: u Generating statistics about CPU, disk, memory, and I/O with no users on the system u Using performance monitoring to establish slow, average, and peak use periods

7. Chapter 14 Establishing Server Benchmarks (continued) u Gathering performance information for slow, average, and peak use when new software is added u Gathering information about growth in server use, number of users, software use and average time users are on the server

8. Chapter 14 Monitoring Server Services n Monitor server services to determine if any are stopped, improperly configured, or possibly hung n Use the Computer Management tool or the Services tool to monitor services (both can be accessed from the Administrative Tools menu)

9. Chapter 14 Windows 2000 Server Default Services

10. Chapter 14 Windows 2000 Server Default Services (continued)

11. Chapter 14 Windows 2000 Server Default Services (continued)

12. Chapter 14 Windows 2000 Server Default Services (continued)

13. Chapter 14 Windows 2000 Server Default Services (continued)

14. Chapter 14 Interpreting Service Information n When you monitor services, the default information that is displayed includes: u The name of each service u A description u Status of the service (started, paused, or halted/not started u Status type (how the service was started) u Logged on as (where the service is running)

15. Chapter 14 Services Display Figure 14-1 Monitoring server services

16. Chapter 14 Troubleshooting Tip n Stop a service carefully because other services may be dependent on it n Check on dependencies by: u Double-clicking the service in the Services tool u Clicking the Dependencies tab

17. Chapter 14 Viewing Service Dependencies Figure 14-2 Service properties

18. Chapter 14 Configuring Service Properties n Configure a service’s properties by double-clicking the service in the Services tool

19. Chapter 14 Service Properties Tabs Table 14-3 Services Properties Tabs

20. Chapter 14 Monitoring Users n To monitor logged on users: u Right-click My Computer and click Manage u Double-click System Tools (if necessary) u Double-click Shared Folders u Click Sessions n To monitor resource use, double-click Shares instead of Sessions as the last step

21. Chapter 14 Monitoring Shared Resources Figure 14-3 Shared resources

22. Chapter 14 Using the Task Manager n Use the Task Manager to monitor: u Applications u Processes u Basic performance

23. Chapter 14 Task Manager Display Figure 14-4 Monitoring started tasks

24. Chapter 14 Starting the Task Manager n To start Task Manager: u Press Ctrl+Alt+Del and then press Task Manager to start the Task Manager u An alternative way to start Task Manager is to right-click an open area of the taskbar and click Task Manager

25. Chapter 14 Other Ctrl+Alt+Del Options n When you press Ctrl+Alt+Del after Windows 2000 Server is booted you have the following options: u Lock Computer u Change Password u Log Off u Task Manager u Shut Down u Cancel

26. Chapter 14 Troubleshooting Tip n When you monitor CPU performance, 100 percent CPU utilization is not a concern if it is temporary, but if it frequently lasts for several minutes instead of several seconds you should troubleshoot the cause

27. Chapter 14 Default Task Manager Information on Processes Table 14-4 Task Manager Information on Processes

28. Chapter 14 Troubleshooting Tip n If you believe a particular program is causing a CPU bottleneck and want to monitor CPU use for its associated process: u Right-click the program in the Applications tab u Click Go To Process u Examine the CPU and CPU Time columns for that process on the Processes tab

29. Chapter 14 Managing Processes n Use the Task Manager to: u Stop a task (application) or process u Stop the process tree (the process and the subprocesses it has started) u Change the priority of a process

30. Chapter 14 Process Priority Settings n A process’s priority can be set to: u Low (-2) u BelowNormal (-1) u Normal (0) u AboveNormal (+1) u High (+2) u Realtime (+15)

31. Chapter 14 Configuring a Process’s Priority Figure 14-5 Resetting a process priority

32. Chapter 14 Troubleshooting Tip n Use the Realtime priority with great caution because it may cause a process to completely dominate a server’s resources

33. Chapter 14 Task Manager Performance Tab n The Task Manager Performance tab enables you to monitor: u CPU performance u Memory performance

34. Chapter 14 Monitoring Performance Data Figure 14-6 Performance data

35. Chapter 14 Task Manager Performance Statistics Table 14-5 Task Manager Performance Statistics

36. Chapter 14 Task Manager Performance Statistics (continued)

37. Chapter 14 Task Manager Performance Statistics (continued)

38. Chapter 14 System Monitor n Use the System Monitor for in-depth monitoring of all kinds of elements on a server, called objects

39. Chapter 14 Default System Monitor Objects Table 14-6 System Monitor Objects

40. Chapter 14 Default System Monitor Objects (continued) Default System Monitor Objects (continued)

41. Chapter 14 Default System Monitor Objects (continued)

42. Chapter 14 Default System Monitor Objects (continued)

43. Chapter 14 CountersCounters n Specific qualities of objects are measured by counters and instances: u Counter: Used by the System Monitor, this is a measurement technique for an object, such as measuring the processor performance by percentage in use u Instance: Used by the System Monitor, when there are two or more types of elements to monitor, such as two or more threads or disk drives

44. Chapter 14 Sample Processor Counters in System Monitor Table 14-7 Sample Processor Counters in System Monitor

45. Chapter 14 Sample Processor Counters in System Monitor (continued)

46. Chapter 14 System Monitor Opening Display Figure 14-7 System Monitor

47. Chapter 14 System Monitor Modes n System Monitor offers three tracking modes: u Chart u Histogram u Report

48. Chapter 14 Using the System Monitor Chart Mode Figure 14-8 System Monitor chart mode

49. Chapter 14 System Monitor Running Inside Microsoft Word n You can run System Monitor inside Microsoft Word to easily capture and print specific charts and information

50. Chapter 14 System Monitor Running Inside Microsoft Word (continued) Figure 14-9 Running System Monitor inside Microsoft Word

51. Chapter 14 Monitoring Page File and Memory Performance n Use the System Monitor Memory and Paging File objects to monitor memory and page file performance

52. Chapter 14 Setting a Memory Counter in System Monitor Figure 14-10 Selecting an object and its counter

53. Chapter 14 Monitoring Paging and Memory in System Monitor Figure 14-11 Monitoring page file performance

54. Chapter 14 Using System Monitor Objects and Counters to Monitor Memory and Paging Table 14-8 Using System Monitor Objects and Counters to Monitor Memory and Paging

55. Chapter 14 Monitoring Memory and Paging (continued)

56. Chapter 14 Monitoring Memory and Paging (continued)

57. Chapter 14 Troubleshooting Tip n A page fault can occur in a kernel process when a page location in virtual memory is lost or corrupted. If this happens, Windows 2000 may crash with a Stop message. Try rebooting to determine if the problem recurs. If it does not, then the problem was simply transient. If it does, employ memory diagnostics to look for a defective memory module.

58. Chapter 14 Interaction Between Software and Memory Use n Monitor the effect of software on memory use, such as looking for leaking memory: u Leaking memory: Failing to return memory for general use after a process is finished using a specific memory block

59. Chapter 14 Monitoring for an Inefficient Program Figure 14-12 Using System Monitor to find an inefficient program process

60. Chapter 14 Using System Monitor Objects and Counters to Monitor Software Use Table 14-9 Using System Monitor Objects and Counters to Monitor Software Use of Memory

61. Chapter 14 Studying Processor Load n Look at three important components when you monitor processor load: u Percent of time the processor is in use u Length of the queue continuing processes waiting to run u Frequency of hardware interrupt requests

62. Chapter 14 Troubleshooting Tip n Plan to gather benchmarks on the frequency of hardware interrupts to have comparative data for troubleshooting hardware problems later on

63. Chapter 14 Using Objects and Counters to Monitor a Processor

64. Chapter 14 Using Objects and Counters to Monitor a Processor (continued)

65. Chapter 14 Using Objects and Counters to Monitor a Processor (continued)

66. Chapter 14 Enabling Disk Monitoring n The Disk Performance Statistics Driver (Diskperf) must be set up to enable disk monitoring n Run Diskperf from the Start button Run option (or from the Command Prompt window) and specify the desired switch, such as Diskperf -y which installs the driver and System Monitor counters for physical and logical drives

67. Chapter 14 Running Diskperf Figure 14-13 Running Diskperf

68. Chapter 14 Using System Monitor Objects and Counters Table 14-11 Using System Monitor Objects and Counters to Monitor Disk Performance

69. Chapter 14 Using System Monitor Objects and Counters (continued)

70. Chapter 14 Using System Monitor Objects and Counters (continued)

71. Chapter 14 Using System Monitor Objects and Counters (continued)

72. Chapter 14 Using System Monitor Objects and Counters (continued)

73. Chapter 14 Monitoring Terminal Services n Use the Terminal Services object in System Monitor to monitor: u Active sessions u Inactive sessions u Total sessions n Use the Terminal Service Session object to monitor selected sessions or all sessions for their affect on the server load

74. Chapter 14 Setting Terminal Service Objects, Counters, and Instances Figure 14-14 Monitoring terminal services

75. Chapter 14 File System Caching n Monitor file system caching so that you can add memory or adjust the memory allocation as needed n File system cache performance is monitored in terms of cache hits and misses: u Cache hit: A situation in which the data needed by an application is found in cache u Cache miss: Occurs when the desired data is not found in cache

76. Chapter 14 Using System Monitor Objects and Counters to Monitor File System Cache Table 14-2 Using System Monitor Objects and Counters to Monitor File System Cache

77. Chapter 14 Tuning Cache n Use the Network and Dial-up Connection tool to tune system cache

78. Chapter 14 Tuning Cache (continued) Figure 14-15 Tuning file system cache

79. Chapter 14 Performance Logs and Alerts n Performance log: Tracks system and network performance information in a log that can be viewed later or imported into a spreadsheet, such as Microsoft Excel n Alert: Provides a warning of a specific Windows 2000 Server system or network event — the warning is sent to designated users

80. Chapter 14 Types of Performance Logs n There are two types of performance logs: u Counter log: Traces information on specific System Monitor objects in selected intervals u Trace log: Traces specified events when they occur

81. Chapter 14 Counter Log File Formats

82. Chapter 14 Configuring a Counter Log Figure 14-16 Configuring a counter log

83. Chapter 14 Counter Log Configuration Tip n Counter logs can use large amounts of disk space and slow performance, thus set the snapshot intervals relatively high, such as at 15 seconds or higher when you monitor for 4 hours or less

84. Chapter 14 Trace Log Elements That Can be Monitored Table 14-14 Trace log elements that can be monitored

85. Chapter 14 Using Alerts n Use an alert to provide a warning each time a particular event occurs, such as when the CPU is at 100 %

86. Chapter 14 Monitoring Caution n Run the Task Manger, System Monitor, performance logging, and alert monitoring sparingly because these all can place an extra load on a server

87. Chapter 14 Chapter Summary n Create a set of benchmarks so that you have comparative information that helps you prevent problems and solve problems after they occur n Monitor server services to make sure that all services are properly configured and started n Use the Task Manager to monitor applications, processes, and performance

88. Chapter 14 Chapter Summary n The Task Manager also enables you to tune a server by tuning process priority n System Monitor is a versatile tool that can be used to monitor all kinds of objects, counters, and instances n Performance logs use System Monitor capabilities to track information for later reference while alerts give you instant notification about a server condition