Converse agora com nosso suporte

Obtenha ajuda em tempo real
Concluir registro

Entrar

Solicitar preços

Entre em contato com o setor de vendas

Foglight 5.9.1 - Performance Tuning Field Guide

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

Memory

Diagnostic Snapshot

Shares Disk

Management Server Tuning

Dashboard Default Timeout

Java Virtual Machine Tuning

Getting Started Foglight JVM Configuration

JVM Options

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

Common Symptoms and Tuning Resolutions

JVM Code Cache

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

MySQL Tuning

Case

Oracle Tuning

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

Undo tablespace Custom Tablespaces

Microsoft SQL Server 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

Agent Tuning

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

Server Log

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

Appendix: Analyzing a Support Bundle

The support bundle is the first line analytic tool for checking the performance of the server. It can be generated through the command-line interface or through the Administration > Setup and Support > Manage Support Bundles dashboard.

This appendix describes what to look for in the support bundle.

•

Server Log

•

Diagnostic Snapshot

•

Analyzing a Performance Report

Server Log

The support bundle contains server log files. The log files are located in <foglight_home>/logs/ and their names adhere to the following format:

ManagementServer_yyyy-mm-dd_hhmmss_nnn.log


	NOTE: Any log entry that contains the keyword ERROR is suspicious.

Topology Sync

Derivation and Rule Service synchronize their state against the topology whenever topology changes. Frequent topology changes may cause frequent synchronization effort, and this is noteworthy. The length of time it takes for a synchronization indicates overall load or topology complexity. Take note of the frequency and length of the following message bracket:

yyyy-mm-dd hh:mm:ss.mmm VERBOSE [TopologySyncQuartzScheduler_Worker-X] com.quest.nitro.service.derivation.DerivationService - Starting derivation topology sync.

...

yyyy-mm-dd hh:mm:ss.mmm VERBOSE [TopologySyncQuartzScheduler_Worker-X] com.quest.nitro.service.derivation.DerivationService - Derivation topology sync finished.

Topology Limits

Foglight™ restricts the number of instances of an object of any type to 10000. When this limit is reached, the event is logged and should be investigated. Either it is an exceptional situation or the limit has to be raised (per type, using the foglight.limit.instances registry variable).

yyyy-mm-dd hh:mm:ss.mmm ERROR [Data-X-thread-Y] com.quest.nitro.service.topology.TopologyService - Failed to create a topology object with name Something: {...}: com.quest.nitro.service.sl.interfaces.topology.TopologyChangeVetoException: The configured limit of 10000 instances of type SQLServer_Backup has been reached.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

Foglight 5.9.1 - Performance Tuning Field Guide

Appendix: Analyzing a Support Bundle

Server Log

Topology Sync

Topology Limits