Hi friends,

Here again a good question like my last one"From where test data come?"

Now we will discuss on Performance counters.
So, start explaining

"What are different Performance counters are? and how they help us in rating the quality of our product?"

Start now...

__________________
Brijesh Jain
brijesh.tester@yahoo.co.in
http://softwaretestingexpertise.blogspot.com

The first and foremost question to address when measuring performance of a web application is "What to measure?" This can be answered by following:

• Identifying and recognizing events that already occur naturally within the application. This method places the burden on those setting up measurements to first identify application-specific milestones.
• Adding instrumentation, by inserting simple monitoring calls like those used by the ARM(Application Response Measurement) standard [ARM1], an existing method for measuring distributed applications. In this approach, developers imbed simple instrumentation calls at logical boundaries in the application’s flow, to enable its subsequent measurement [ARM2]. This frees the measurement tool from the need to know anything about the application, but places the burden on application developers to instrument their code by inserting markers at key points

The following 10 points highlight the purpose of measuring performance of any web application -

1. Verifying that an application meets its service level objectives
2. Detecting abnormal application behavior (typically, slow response)
3. Identifying bottlenecks in application components
4. Comparing builds, versions, or releases of an application
5. Comparing two applications that perform comparable functions
6. Verifying that a system will be able to handle the projected traffic
7. Determining how many users a server environment can handle
8. Predicting bottleneck components as workload levels grow
9. Comparing builds, versions, or releases of an application
10. Identifying components that fail after extended use

Good dsharma;
Good answer from your side, but friend i am looking for counters like request per second, total number of request per sec, no of page fault, like this.

What so ever you have answered is related to performance but not the performance counter.I hope more from your side.So, please reply , i am waiting for your post.

__________________
Brijesh Jain
brijesh.tester@yahoo.co.in
http://softwaretestingexpertise.blogspot.com

When it comes to manual testing, we rely on the factors that I have jotted for performance. The counters you are talking about is taken care by Automated Testing using LoadRunner or SilkPerformer, etc. wherein we have to give various conditions to calculate the performace of an application to the last second.

Performance Monitoring is a complex subject and in some ways more of an art than a science. It can be daunting to be confronted with a choice of over a thousand performance counters to choose from. Which ones are important to monitor on a regular basis and which ones can be largely ignored? A lot depends on the role of the system you want to monitor and whether you're talking about capacity planning, ensuring availability, scaling upwards, monitoring for possible problems, or troubleshooting issues that have arisen.

System\System Up Time counter, tells you how many seconds it's been since your server last rebooted.

__________________
Brijesh Jain
brijesh.tester@yahoo.co.in
http://softwaretestingexpertise.blogspot.com