Performance can be understood as an indicator. In a certain environment, the system responds within a certain period of time.
L performance from the user's perspective
Response time of the software to user feedback. Note: If a user obtains a large amount of data, it will take a lot of time, but it takes a long time for the user to optimize data presentation (for example, to operate 1000 data records in the background, you can present 10 records first, and the other 990 records are still running, but you cannot feel it. C/S architecture is widely used by programmers)
L performance from the Administrator's perspective
Administrators not only need to know the system response time to users, but also pay more attention to the usage of hardware (servers: Web and DB) during user operations. For example, if the number of users reaches a certain level (1000 people are online at the same time), can the server memory and CPU be used properly. Through these understandings, administrators can better manage servers, increase capacity, and replace hardware to ensure smooth network access.
L performance from the development perspective
Developers do not just complete the program, so that users can barely use it. For a qualified programmer, the developed program is convenient and correct for users. Developers are more concerned about the root cause of poor performance in those areas of the program; those areas may cause possible faults.