Managing the request topology is primary tool for Java and .NET scaling
In Java, each Unique Request Type is stored as a topology object. Request Types then create distinct topology objects for each server/instance of that request type.
If you turn on additional breakdowns(component,tier,etc), additional topology objects are created
How to calculate Java sizing
The Java Equations
- WebLogic/Websphere
Unit Count = ((0.033*Requests + 12) * JVMs) + 8
- JBoss/Tomcat/OAS
Unit Count = ((0.016* Requests + 7) * JVMs) + 8
- X-Agent
- Unit Count = ((0.033*Requests + 1) * JVMs) + 8
-Add Tier and Component Technology Breakdown
- Multiple overall, unit count for each “system” monitored on the nexus by 2x
- Application and Server Breakdowns will have impact too, but aren't included
- Memory Tracking: Add 20 units total
How to calculate .NET sizing
.NET Equations
How to manage overall overhead
https://support.quest.com/foglight/kb/75622
https://support.quest.com/foglight/kb/62707
-Use the RequestDetailRules.Setting the request details at the default level means it will double the scope for ALL of the requests that hit this Nexus which could be expensive.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center