Performance advisor types and purposes

Two performance advisors are available: the Orientador de Desempenho e Diagnóstico and the performance advisor in Tivoli® Performance Viewer.

The Orientador de Desempenho e Diagnóstico 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. Orientador de Desempenho e Diagnóstico and Tivoli Performance Viewer advisor. The following chart shows the differences between the Orientador de Desempenho e Diagnóstico and the Tivoli Performance Viewer advisor:
  Orientador de Desempenho e Diagnóstico 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: Esse tópico faz referência a um ou mais arquivos de log do servidor de aplicativos. Como uma recomendação alternativa, é possível configurar o servidor para usar a infraestrutura de log e rastreio do High Performance Extensible Logging (HPEL) em vez de usar os arquivos SystemOut.log , SystemErr.log, trace.log e activity.log em sistemas distribuídos e IBM® i. Também é possível usar HPEL em conjunção com os recursos de criação de log z/OS® nativos. Se você estiver usando HPEL, será possível acessar todas as informações de log e rastreio usando a ferramenta de linha de comandos LogViewer a partir do diretório bin do perfil do servidor. Consulte as informações sobre a utilização do HPEL para resolução de problemas dos aplicativos para obter mais informações sobre o uso do HPEL.

Ícone que indica o tipo de tópico Tópico de Conceito



Ícone de registro de data e hora Última atualização: July 9, 2016 7:50
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=cprf_choosingperfadvisor
Nome do arquivo: cprf_choosingperfadvisor.html