Chatee ahora con Soporte

Obtener ayuda en vivo
Completar registro

Iniciar sesión

Solicitar precios

Comuníquese con Ventas

Foglight 5.9.4 - Performance Tuning Field Guide

Navegación de contenido

Characteristics of Poor Performance in Foglight Parameters that Affect Foglight Performance Critical Areas that Can Affect Foglight Performance Identifying Performance Problems

Hardware and Operating System Tuning

Running on Virtual Hardware

Performance Challenges CPU

Ready Time

Diagnostic Snapshot

Management Server Tuning

Dashboard Default Timeout

Java Virtual Machine Tuning

Getting Started Foglight JVM Configuration

-XX:+UseConcMarkSweepGC -Xmx and -Xms -XX:NewSize, -XX:MaxNewSize, and -XX:NewRatio -XX:MaxPermSize -Xss

Common Symptoms and Tuning Resolutions

Backend Database Tuning

Initial Database Configuration Settings

Monitoring and Managing Database Size Backup and Recovery Recommendations init.ora Configuration

Sample init.ora:

Database Maintenance Recommendations

Case

How the Management Server Uses the Database Index Management Memory Block Size Oracle Striping Oracle Tablespaces

Undo tablespace Custom Tablespaces

Microsoft SQL Server Tuning PostgreSQL Tuning Troubleshooting

Management Server Load Preventing Database Connections

High Availability (HA) Tuning

Tuning Connection Issues in an HA Implementation Managing Hosts with Multiple Network Interfaces JDK with IPv6 on Linux Management Server Automatically Restarted Other JGroup Related Issues and Information

Topology Changes and Topology Churn Canonical Data Transformations (CDTs) Agent Weight / Environment Complexity Large Topologies Sampling Frequency XML-HTTP Agent Adapter Dropped Agent Manager Log Messages Java EE Technologies

Appendix: Performance Health Check

Is the Server Getting the Right Amount of Memory?

Management Server Memory is Healthy if ... Management Server Memory Checks Possible Actions

Is the Server Getting Enough CPU?

Management Server CPU is Healthy if ... Management Server CPU Checks Extended Browser Interface Checks Possible Actions

Is the Database too Slow?

The Database is Healthy if ... Database Checks Possible Actions

Is the Database Growth Reasonable?

Database Growth is Healthy if ... Database Checks Possible Actions

Is There Too Much Data to Process?

Data Volume is Healthy if ... Data Volume Checks Possible Actions

Is the Model Stable?

The Model is Healthy if ... Model Checks Possible Actions

Are Too Many Alarms Firing?

The Number of Alarms is in a Healthy State if... Alarms Checks Possible Actions

Is the Business Logic Properly Tuned?

Business Logic is Healthy if... Business Logic Checks Possible Actions

Are There Too Many User Requests?

User Activity Is Healthy If... Possible Actions

Appendix: Analyzing a Support Bundle

Topology Sync Topology Limits

Diagnostic Snapshot

Memory Consumption Threads, Deadlocks, and Overall CPU Usage Useful Information ---- jboss.system:type=ServerInfo ---- jboss.jca:service=ManagedConnectionPool,name=jdbc/nitrogen ---- jboss.web:type=RequestProcessor,* ---- com.quest.nitro:service=Derivation

Derivation Related Issues

---- com.quest.nitro:service=Topology

Topology Related Issues

---- com.quest.nitro:service=DataCacheEviction

Analyzing a Performance Report

Server Rule Information System-wide Topology Changes JVM Memory Usage Management Server Garbage Collectors JDBC Connection Pool Derivation Rulette

Overview

Performance is a measure of the efficiency of an application running in an environment or of the overall efficiency of multiple applications running in the same environment.

You tune performance in order to optimize it.

•

Characteristics of Poor Performance in Foglight

•

Parameters that Affect Foglight Performance

•

Critical Areas that Can Affect Foglight Performance

•

Identifying Performance Problems

Characteristics of Poor Performance in Foglight

The following items characterize poor performance in the Foglight® environment:

•

poor performing (slow) browser interface

•

•

high CPU load for the Foglight Management Server process

•

high CPU load for the database backend process

•

excessive memory utilization (or out of memory)

•

long-running SQL statements

Parameters that Affect Foglight Performance

Foglight® is a complicated system, and its runtime performance depends on many variables within the environment.

The following parameters have an effect on Foglight performance:

•

the processing power of the host running the Management Server

•

the memory of the host running the Management Server

•

the memory allocated for the Management Server process (heap)

•

the database backend type (MySQLTM/Oracle®)

•

the processing power of the host running the database backend

•

the memory of the host running the database backend

•

the database setup

•

the number of Foglight Agent Managers

Foglight’s runtime performance also depends on what it is monitoring.

Critical Areas that Can Affect Foglight Performance

It can be difficult to determine that Foglight® performance is suffering and then identify the appropriate steps to take. This guide provides information about the various things that can have an effect on overall performance and describes the applicable performance-related options.

The areas that can have an effect on overall performance are:

•

Hardware and Operating System Tuning

•

Management Server Tuning

•

Java Virtual Machine Tuning

•

Backend Database Tuning

•

High Availability (HA) Tuning

•

Herramientas de autoservicio: Base de conocimientos; Notificaciones y alertas; Soporte de productos; Descargas de software; Documentación técnica; Foros de usuarios; Tutoriales en video; Aviso de actualizaciones de páginas web (RSS)

Comuníquese con nosotros: Obtenga asistencia con las licencias; Soporte Técnico; Ver todos

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación

© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center