Here you go CA Wily Customer Experience Manager in my way
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
CA Wily identifies the potential performance problems by analyzing the user transactions when we do performance testing of scalable web apps and thus allows the organization to understand and respond to the end user, which is within organization. It addresses all the performance issues in the configuration of middle ware architecture like connections to the database, active number of threads in the application server, heap usage and memory leak issues.
Pros
- Heap Consumption in the Application servers and its traces throughout the test scenarios.
- Active number of database connections from application server to the database server.
- It provides the CPU usage in the JVM and also provides if all the instances of application server are having load while running the test on the load balancing server.
- Traces the active number of threads in each node of application server.
Cons
- To kill the thread explicitly in the server as per our need.
- To explicitly invoke the garbage collection so as to monitor the load as per our desire.
- Sampling frequency to be reduced to get more deterministic of some counters.
- Determine the first response byte from the server.
Likelihood to Recommend
CA Wily is well suited for monitoring the load balanced application nodes and determine their main performance bottlenecks like if problem exists in heap or in some connection issues. But I think when it comes to providing the entire report of the application, it is less appropriate as there is no way to create the entire report of the test for all the counters monitored. Also there is no way to detect some issues based on the system configuration.