In Windows, you can also use osw to trace the historical system performance.

In Windows, you can also use osw to trace the historical system performance.
1. difficult background of Windows System Performance Analysis

In Linux/Unix, to keep track of historical performance, we generally deploy nmon for performance monitoring collection and storage, but it is not in Windows.

For Windows systems, it is always difficult to analyze historical performance.

In fact, ORACLE has a monitoring tool called OSWatcher, which can be used not only on Linux/Unix, but also on Windows, calledOS Watcher For Windows (OSWFW)To solve the problem that historical performance cannot be queried on Windows.

2. Windows versions supported by OSWFW

Windows XP (x86 & x64) Windows 7 (x86 & x64) Windows 8 (x86 & x64) Windows 2003 R1 & R2 (x86 and x64) Windows 2008 R1 & R2 (x86 & x64) Windows 2012

3. OSWFW metrics

Cache LogicalDisk Memory Netstat PagingFile PhysicalDisk Process Processor Server_Work_queue System Thread

4. Software official instructions and

See metalink documentation: the current version of 433472.1 is oswfw_2_5.1

5. OSWFW deployment on Windows

C: \> unzip oswfw_2_5.1.zip C: \ oswfw_2_5.1 & gt; oswatcher 60 10000

Parameter value description: 60: collected every 60 seconds

10000: 10000 hours of continuous operation

After startup, an Archive file is generated under c: \ oswfw_2_5.1 to store the data collected by monitoring. The data is saved in csv format.

6. Chinese Version OSWFW deployment method on Windows 6.1 Chinese Version oswfw running on Windows

According to the metalink Document on the oracle official website, oswfw can only run on the English version of Windows. However, I have tested that the Chinese version of Windows can also run OSWFW by modifying the cmd window code page of windows. When oswatcher is started, the following information is reported:

Start of Operating System Watcher for Windows At this time, there should be no 6.1. C: \ oswfw_2_5.1>

6.2 The Windows code page needs to be modified when running oswfw in Windows

C: \ oswfw_2_5.1> chcp 437 Active code page: 437

6.3 start oswfw

C: \ oswfw_2_5.1 & gt; oswatcher 60 10000

Parameter value description: 60: collected every 60 seconds

10000: 10000 hours of continuous operation

7. OSWFW deployment on Windows in RAC dual-host environment 7.1 OSWFW special adjustment in RAC Environment

(1) Rename the OSWPrivNet. config. template file to OSWPrivNet. config

(2) Add the private IP addresses of all nodes to the OSWPrivNet. config file, as shown in figure

# Start of OSWPrivNet. config file # Put the IP addresses for all Interconnect interfaces of all nodes on a single line # Remove the "#" character from the address line. The following are examples only: 192.168.1.100 192.168.1.101 # End of OSWPrivNet. config file

7.2 RAC environment startup Method

C: \ oswfw_2_5.1> oswatcher 60 10000 RAC

8. Stop OSWFW8.1 stop OSWFW on a Single Node

C: \ oswfw_2_5.1> oswatcher stop

8.2 stop OSWFW of all nodes in RAC

C: \ oswfw_2_5.1> oswatcher stop curiousgeorgel

Author: LI Junjie (Network Name: Step-by-Step), engaged in "system architecture, operating system, storage device, database, middleware, application" six levels of systematic performance optimization work

Join the system performance optimization professional group to discuss performance optimization technologies. GROUP: 258187244