《WebSphere应用服务器性能调优工具介绍》由会员分享，可在线阅读，更多相关《WebSphere应用服务器性能调优工具介绍（35页珍藏版）》请在金锄头文库上搜索。
1、WebSphere Application Server Performance Tuning Toolkit,Feb, 2012,Sui Peng Fei (),Why we use this toolkit ?,1) Friendly and easily understood UI 2) No additional effort to install or configure,Quick Start : Launch the Performance Tuning Toolkit,Unzip the zip file and launch the PerfTuningToolkit.exe
2、. You will see the workbench!,Quick Start : Connect to your WAS,From the Hosts View, double click the new created host , and click “Ok” in next prompt dialog.,Quick Start : Start Monitoring,Double click the added host and click “OK” in next message box to start all the servers,Quick Start : Monitor
3、the dashboard,The dashboard will monitor all the key status of servers (include Application Servers and Proxy Servers) in the latest monitoring interval (the monitor interval is multiple of the data collection interval which was set in the preference panel) The color of performance data will turn re
4、d if some abnormal events were detected in current monitoring interval, it only represent the current status. There will also be a warning mark in the second column as long as any error ever occurs and it will leave unless you clear it. So the warning marks can represent history abnormal events.,1.
5、Performance,2. Errors,3. System status,4. Customized alert (rule based),Quick Start : Monitor a server - 1,Double click any panel in the dashboard, you will go to the monitor page of that server,Quick Start : Monitor a server - 2,Adjust the statistics interval: this function will be useful when the
6、curve jitter violently,Quick Start : Monitor a server - 3,Hidden the chart that is useless for you, this will not affect the data page,Quick Start : View detailed data of each component,Switch to detail data page by clicking the point in the monitor page, or click that tabs at the bottom,Quick Start
7、 : Interval concept of performance monitoring,Pay attention to the interval of Dashboard, Charts and the Data Collections.,Monitoring Interval: 1). Multiple of Data Collection Interval. 2). Can be adjusted at any time 3). Can only be up to the current time,Analysis Interval: 1). Multiple of Data Col
8、lection Interval. 2). Can be adjusted at any time 3). The end time may not be the current time,Data Collection Interval: 1). Can only be set in the preference panel. 2). Can not be adjusted at run time.,Monitoring Interval,Analysis Interval,Data Collection Interval,Setup the Topology : 1. Applicatio
9、n Server: WebSphere Application Server version 7.0 or later. 2. Data Base: Derby/Db2. 3. Use the latest Jmeter to as the stress client. 4. Download the Websphere Application Server Performance Tuning Toolkit.,Application Server Cluster,Test Client,Proxy Server,Dmgr,Data Base,Server3,Server4,Server1,
10、Server2,Install the test application and start stress : 1. A separate application installation guide will be provided for reference 2. A Jmeter script file and Jmeter user guide will be provided for reference,Scenario description : 1. Use a modified Daytrader2.0 benchmark to simulate application wit
11、h a connection leak problem. 2. Use PTT detect the connection leak problem,Demo: Synchronization Blocking,Demo: Code to trigger the Synchronization Blocking problem,Start Demo now!,Quick Start : Other operations - 1,Users can generate thread dump, heap dump, get connection contents and enable trace
12、when connected to the cell.,Quick Start : Other operations - 2,GUI of connection content panel. More and more functions will be added to facilitate the performance problem determination,Quick Start : Edit the rules - 1,Data from all components will go through the rule engine. Some rules has been def
13、ined in the rule file,The existing rules: If the used heap reaches the 85% of maximum heap size, it will generate a runtime alert. If the used thread pool reaches 90% of the max pool size, it will generate a threadpool alert. If the average CPU usage reaches 90%, it will generate a runtime alert. If
14、 some servlet errors occur, it will generate a servlet alert. If some JDBC connection timeout occur, it will generate a connection alert If there are more then 1000 prepared statement discarded, it will generate a connection alert If there are some thread waiting for connection, it will generate a c
15、onnection alert If some JCA connection error occur, it will generate a JCA alert If there is no room for new session, it will generate a session alert If some hung threads are declared, it will generate a threadpool alert If some transactions rolled back, it will generate a transaction alert If some
16、 transactions timeout, it will generate a transaction alert If some proxy request failed, it will generate a proxy alert If a servlet performance decline detect it will generate a servlet alter If a jdbc performance problem detect, it will generate a connection pool alert,Quick Start : Edit the rules - 2,Users can modify these rules or create their own rules in the rule editor.,Demo: Code to trigger the Connection Leak problem,
