Software Performance Overview

1.1 Software Performance Basics

1.1.1 concept of Software Performance

Software performance is a very important non-functional feature that corresponds to software functions. It indicates the time and

Time and Resource Economics requirements.

1.1.2 understanding of software performance by different roles

(1) system user: response time. After a user executes a function operation, the result of this operation is displayed to the user in the software.

(2) system O & M personnel: stable and scalable. It mainly focuses on performance optimization.

(3) system developers: Architecture, database, and thread synchronization.

2. Importance of Software Performance

For a software system, the faster the running time, the less storage resources and other resources occupied by the system, the better the software performance. Performance is the resources required by the software and the time it takes to complete the work. When the functions are the same, performance is an important factor to measure the effect of a task.

1.2 common performance indicators

1.2.1 response time: the time consumed by the software system to serve the user. Operation-> response.

Three cases:

Idle response time, busy response time, and peak response time.

1.2.2 concurrent users: number of user requests that the system can simultaneously process.

There are also registered users and online users.

Average number of concurrent users: the number of concurrent users under normal system access.

Maximum number of concurrent users: the number of concurrent users under peak access. (Reflects the processing capability of the system, which is often defined as an important performance indicator during demand analysis ).

1.2.3 throughput: the number of customer requests processed by the system per unit time. In bytes.

RPS: Number of requests per second. The maximum number of requests that can be processed per second.

PPS: page count/second. The number of pages that can be displayed per second.

PV: page count/day. The total number of page views per day.

TPS: Transaction/second. The number of transactions that can be processed per second.

QPS: Query/second. The number of query requests that can be processed per second.

1.2.4 server performance counters.

Some data indicators play a key role in monitoring and analysis in performance testing.

1.4 Software Performance Lifecycle Model

Performance Requirement Analysis overview design detailed design coding unit performance test integration performance test

System Performance Test

Software Performance Overview