Performance advisor types and purposes

Two performance advisors are available: the 效能和診斷顧問 and the performance advisor in Tivoli® Performance Viewer.

The 效能和診斷顧問 runs in the Java™ virtual machine (JVM) process of application server; therefore, it does not provide expensive advice. In a stand-alone application server environment, the performance advisor in Tivoli Performance Viewer runs within the application server JVM.

The performance advisor in Tivoli Performance Viewer provides advice to help tune systems for optimal performance and provide recommendations on inefficient settings by using collected Performance Monitoring Infrastructure (PMI) data. Obtain the advice by selecting the performance advisor in Tivoli Performance Viewer.

In a WebSphere® Application Server, Network Deployment environment, the performance advisor in Tivoli Performance Viewer runs within the JVM of the node agent and can provide advice on resources that are more expensive to monitor and analyze. The Tivoli Performance Viewer advisor requires that you enable performance modules, counters, or both.

Table 1. 效能和診斷顧問 and Tivoli Performance Viewer advisor. The following chart shows the differences between the 效能和診斷顧問 and the Tivoli Performance Viewer advisor:
  效能和診斷顧問 Tivoli Performance Viewer advisor
Start location Application server Tivoli Performance Viewer client
Invocation of tool Administrative console Tivoli Performance Viewer
Output
  • The SystemOut.log file
  • The administrative console
  • JMX notifications
Tivoli Performance Viewer in the administrative console
Frequency of operation Configurable When you select refresh in the Tivoli Performance Viewer administrative console
Types of advice

Performance advice:

  • Object Request Broker (ORB) service thread pools
  • Web container thread pools
  • Connection pool size
  • Persisted session size and time
  • Prepared statement cache size
  • Session cache size
  • Memory leak detection
Diagnostic advice:
  • Connection factory diagnostics
  • Data source diagnostics
Connection usage diagnostics
  • Detection of connection use by multiple threads
  • Detection of connection use across components

Performance advice:

  • ORB service thread pools
  • Web container thread pools
  • Connection pool size
  • Persisted session size and time
  • Prepared statement cache size
  • Session cache size
  • Dynamic cache size
  • Java virtual machine (JVM) heap size
  • DB2® Performance Configuration wizard
Note: 這個主題參照一或多個應用程式伺服器日誌檔。 此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.logSystemErr.log, trace.logactivity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。

指出主題類型的圖示 概念主題



時間戳記圖示 前次更新: July 9, 2016 11:11
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=cprf_choosingperfadvisor
檔名:cprf_choosingperfadvisor.html