Performance Testing Into

CPU interrupts per second

Is the avg. number of hardware interrupts a processor is receiving and processing each second.

Memory pages/second

Number of pages written to or read from the disk in order to resolve hard page faults. Hard page faults are when code not from the current working set is called up from elsewhere and retrieved from a disk.

Rollback segment

the amount of data that can rollback at any point in time.

Hits per second

the no. of hits on a web server during each second of a load test.

Thread counts

An applications health can be measured by the no. of threads that are running and currently active.

Memory use

Amount of physical memory available to processes on a computer.

Disk time

Amount of time disk is busy executing a read or write request.

Processor usage

Amount of time processor spends executing non-idle threads.

Committed memory

Amount of virtual memory used.

Spike testing

Tests the software's reaction to sudden large spikes in the load generated by users.

Load testing

Checks the application's ability to perform under anticipated user loads. The objective is to identify performance bottlenecks before the software application goes live.

Stress testing

Involves testing an application under extreme workloads to see how it handles high traffic or data processing. The objective is to identify breaking point of an application.

Endurance testing

Is done to make sure the software can handle the expected load over a long period of time.

Disk queue length

Is the avg. no. of read and write requests queued for the selected disk during a sample interval.

Garbage collection

It has to do with returning unused memory back to the system. Garbage collection needs to be monitored for efficiency.

Network output queue length

Length of the output packet queue in packets. Anything more than two means a delay and bottlenecking needs to be stopped.

What are the types of Performance Testings?

Load testing Stress testing Endurance testing Spike testing Volume testing Scalability testing

Private bytes

Number of bytes a process has allocated that can't be shared amongst other processes. These are used to measure memory leaks and usage.

Performance Testing

Performance Testing is a type of testing to ensure software applications will perform well under their expected workload.

Network bytes total per second

Rate which bytes are sent and received on the interface including framing characters.

Bandwidth

Shows the bits per second used by a network interface.

What is the focus of Performance Testing?

Speed - Determines whether the application responds quickly Scalability - Determines maximum user load the software application can handle. Stability - Determines if the application is stable under varying loads

Maximum active sessions

The maximum number of sessions that can be active at once.

Amount of connection pooling

The number of user requests that are met by pooled connections. The more requests met by connections in the pool, the better the performance will be.

Scalability testing

The objective of scalability testing is to determine the software application's effectiveness in "scaling up" to support an increase in user load. It helps plan capacity addition to your software system.

Page faults/second

The overall rate in which fault pages are processed by the processor. This again occurs when a process requires code from outside its working set.

Hit ratios

This has to do with the number of SQL statements that are handled by cached data instead of expensive I/O operations. This is a good place to start for solving bottlenecking issues.

Response time

Time from when a user enters a request until the first character of the response is received.

Volume testing

Under Volume Testing large no. of. Data is populated in database and the overall software system's behavior is monitored. The objective is to check software application's performance under varying database volumes.

Top waits

are monitored to determine what wait times can be cut down when dealing with the how fast data is retrieved from memory

Database locks

locking of tables and databases needs to be monitored and carefully tuned.

Throughput

rate a computer or network receives requests per second.