1. Virtual Memory Tuning   You can improve a server’s performance by optimizing the way the paging file is used   You may want to size the paging file so that it is as large as it needs to be for typical usage conditions   Consider fixing the paging file size so that the server needn’t spend any resources expanding the paging file   If a server has multiple hard disk drives, you might consider creating a paging file on each physical hard disk drive on the system or on a separate very fast hard drive

2. Tracking General Health Of The System   The fastest, easiest way to monitor immediate system’s general health is to use Task Manager or Process Resource Monitor   Use Task Manager to track running applications and processes and determine resource usage   Process Resource Monitor is much more detailed than the default Task Manager view

3. Tracking Events And Using Event Viewer   An event is defined as any significant occurrence in the operating system or an application that should be recorded for tracking purposes   Various events can be tracked - events that record information, warnings, errors, and auditing   Event logging is controlled by the Event Log service   Three event logs: Application Contains events logged by applications Security log Contains events you’ve set for auditing with local or global group policies System Log Contains events logged by Windows Server 2003 and its components

4. Tracking events on multiple computers   You can use Event Viewer to view events on other computers on your network   You must be logged on as an administrator or be a member of the Administrators group to view events on a remote computer   You can view events on systems running Windows Server 2003, Windows XP, Windows 2000, and Windows NT   For checking the event logs on many systems: Eventquery A command-line tool for examining the event logs on local and remote systems EventComb A Windows Server 2003 Resource Kit tool for searching the event logs on multiple systems

5. Performance Analysis and Logging   Establishing Performance Baselines   Comprehensive System Monitoring   Resolving Performance Bottlenecks   Performance Logging   Analyzing Performance Logs   Creating Performance Alerts

6. Establishing Performance Baselines   Several types of baselines you can use: Post-installation baselines Typical usage baselines Test baselines   Typical usage baseline is more important   Keep the baseline in sync with how the server is used Baseline

7. Comprehensive System Monitoring   System Monitor is a tool designed to track and display performance information in real time   Each performance item you want to monitor is defined by the following three components: Performance objects Object instances Performance counters   The most commonly tracked performance objects are Memory, PhysicalDisk, and Processor   Consider monitoring performance remotely

8. Resolving Performance Bottlenecks   A bottleneck is any condition that keeps a computer from performing at its best   Memory is usually the main bottleneck on both workstations and servers   The processor, disk subsystem, and the networking components can be bottlenecks too   The server cannot perform at its optimal level when you install the minimum or recommended amount of memory

9.   Before you set out to monitor memory usage: Check that the computer has the recommended amount of memory for the operating system and the applications it is running Look at the amount of memory available and the amount of virtual memory being used Look at the way the system is using the paged pool and non- paged pool memory Look at the way the system is using the paging file Resolving Performance Bottlenecks

10.   After eliminating memory as a potential bottleneck, examine the system’s processor usage   Processor bottlenecks can occur if a process’s threads need more processing time than is available   On multiprocessor systems, you might need to rule out processor affinity as a cause of a processor bottleneck Resolving Performance Bottlenecks

11.   System’s hard disks are rarely the primary reason for a bottleneck   It is more likely that a system is doing a lot of disk reads and writes because there isn’t enough physical memory available   The network is critically important - It may not matter how fast your computers are or how fast your servers are   In most cases, the latency users experience is beyond your control   Bandwidth available to your servers is a factor you can control Resolving Performance Bottlenecks X

12. Performance Logging   Record performance information for replay in Performance Monitor at a later date   Export logging data to spreadsheets or databases for analysis and report generation   Create performance logs by using Performance Monitor: Counter logs Trace Logs

13. Analyzing Performance Logs   Once you set up performance logging, you can use the logs to record performance data   The method of viewing the log data depends on the log type and its format

14. Creating Performance Alerts   Use performance alerts to notify you and others when certain events occur or when certain performance thresholds are reached   Generate events that are logged in the Application event log and to start applications and performance logs

15. Project Server 2003 - Changes that Impact Performance   Functional changes Unexpected growth in number of users, projects, resources etc.   Data complexity changes Size of projects, formulas in custom fields, task outline codes, multiple baselines etc. => impact on save/open time