Performance monitoring is the process that we need to acquire for all web based applications in the testing environment before an application moves in to production. Wily Introscope is a tool which helps us in monitoring the applications.
Wily Introscope:
Introscope — one of the technology foundations of Wily’s Customer Success Management — is a proven solution that provides IT teams with everything they need to ensure superior application infrastructure performance:
• 24x7 Application Monitoring
• Incident Detection and Notification
• Rapid Triage
• Root Cause Diagnosis
• Trend Analysis/Planning
Organizations around the world have made Introscope® their solution of choice for lowering the costs and risks associated with deploying, managing, and supporting applications.
Wily Introscope can monitor method level response time statistics of an application Server. The tool can be extensively used to monitor a weekly statistics for your application to be tested. It can gather CPU and memory level statistics .It can be used to raise alarm, if a threshold limit is being reached. This helps the developer to quickly look into the issue any time any hour. The data that it provides is both Graphical and excel representation which helps anyone to understand where and what the issue is. It had a feature called Dashboard which helps us in customizing the information that we need to monitor.
Statistics Measured:
1. GC Heap size.
2. No. of processors used for the application.
3. CPU utilization.
4. Thread details
5. Pool size.
6. Session details.
Considering GC Heap size we can get details regarding
Bytes Total, the memory allocated for the particular application and
Bytes in use, memory currently in use after total being allocated,.
In historical range options, we select the time frame of two hours (half an hour before the test run and half an hour after test run). This is done to analyze how the statistics differ before and after the test run. Generally the graph should be a saw tooth graph which denotes that GC ( Garbage Collection ) is taking place regularly at periodic intervals, which inturn means that the objects are created and released (discarded) at regular intervals by JVM. GC should be equi proportional. From the graph we should note down the highest memory consumed and simultaneously look in to the logs for analysis. The number of live sessions in a test run should be equal to number of users ( logged in to the application ). The number of active sessions during a test run denotes the number of users who are active and accessing the application concurrently. If there are any errors in the test run, they can be identified from the number of live sessions. The active threads analysis tells us the concurrent hits per second taking place in an application.
In a 3 – tier architecture, the request taking place between the web server and application server constitutes the active threads, which could also be obtained from the wily Introscope. Measuring these statistics we can give observation about the application.
Wily Introscope can monitor method level response time statistics of an application. This tool is extensively used to monitor statistics of the application to be tested. Here are certain examples to monitor the behavior of an application, carry out a causal-analysis for the under performance of the application and find out the possible changes which can help the application to perform better if subjected to the similar conditions.
Wily Introscope:
Introscope — one of the technology foundations of Wily’s Customer Success Management — is a proven solution that provides IT teams with everything they need to ensure superior application infrastructure performance:
• 24x7 Application Monitoring
• Incident Detection and Notification
• Rapid Triage
• Root Cause Diagnosis
• Trend Analysis/Planning
Organizations around the world have made Introscope® their solution of choice for lowering the costs and risks associated with deploying, managing, and supporting applications.
Wily Introscope can monitor method level response time statistics of an application Server. The tool can be extensively used to monitor a weekly statistics for your application to be tested. It can gather CPU and memory level statistics .It can be used to raise alarm, if a threshold limit is being reached. This helps the developer to quickly look into the issue any time any hour. The data that it provides is both Graphical and excel representation which helps anyone to understand where and what the issue is. It had a feature called Dashboard which helps us in customizing the information that we need to monitor.
Statistics Measured:
1. GC Heap size.
2. No. of processors used for the application.
3. CPU utilization.
4. Thread details
5. Pool size.
6. Session details.
Considering GC Heap size we can get details regarding
Bytes Total, the memory allocated for the particular application and
Bytes in use, memory currently in use after total being allocated,.
In historical range options, we select the time frame of two hours (half an hour before the test run and half an hour after test run). This is done to analyze how the statistics differ before and after the test run. Generally the graph should be a saw tooth graph which denotes that GC ( Garbage Collection ) is taking place regularly at periodic intervals, which inturn means that the objects are created and released (discarded) at regular intervals by JVM. GC should be equi proportional. From the graph we should note down the highest memory consumed and simultaneously look in to the logs for analysis. The number of live sessions in a test run should be equal to number of users ( logged in to the application ). The number of active sessions during a test run denotes the number of users who are active and accessing the application concurrently. If there are any errors in the test run, they can be identified from the number of live sessions. The active threads analysis tells us the concurrent hits per second taking place in an application.
In a 3 – tier architecture, the request taking place between the web server and application server constitutes the active threads, which could also be obtained from the wily Introscope. Measuring these statistics we can give observation about the application.
Wily Introscope can monitor method level response time statistics of an application. This tool is extensively used to monitor statistics of the application to be tested. Here are certain examples to monitor the behavior of an application, carry out a causal-analysis for the under performance of the application and find out the possible changes which can help the application to perform better if subjected to the similar conditions.
No comments:
Post a Comment