Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight 6.0.0 - Performance Tuning Field Guide

Overview Hardware and Operating System Tuning Management Server Tuning Java Virtual Machine Tuning Backend Database Tuning High Availability (HA) Tuning Agent Tuning Store and Forward Processing Appendix: Performance Health Check Appendix: Analyzing a Support Bundle

Business Logic Checks

•
With little data coming in and no browser interface operations (including report generation), observe the CPU utilization on the Foglight® Management Server. If it is high, and the memory settings for the Management Server are reasonable, and it is the Management Server that is consuming the CPU, then it is likely that there is too much business logic running.
•
Look at the rulette and derived metric expression counts. If they are greater than 100,000, or more than two times the total number of objects in the system, then it is possible there is too much business logic running.

Possible Actions

•
Revisit the customizations that have been applied.
•
Turn off rules.
•
Clean up the model by removing items that are no longer needed.
•
Contact Quest for information on how to optimize business logic per cartridge or domain.

Are There Too Many User Requests?

In Foglight®, user requests include browser interface requests and report generation. It is possible that Foglight can become slow simply because there are too many users trying to access the system.

User Activity Is Healthy If...

•
The number of users is low (less than 10).
•
The number of scheduled reports is low.
•
Users report reasonable response time (5 to 15 seconds for a page to be drawn).
•
Pages perform slowly only rarely.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation