- Slow transactional response with or without application workload
- Failure to meet the processing rate, for example, 1,000 submitted orders per second
- Failure of the application to serve the required number of concurrent users
- Non-responding application under workload
- Transactional errors during application workload, which could be reported by application users or seen in the application log files
- Mismatch between application workload and resource utilization, for example, CPU utilization is 90 percent with a few users or memory utilization is 70 percent even during no user activity
- Abnormal application behavior under certain conditions, for example, the application's response slows down daily at midnight
- All other aspects of application failure to meet functional or nonfunctional requirements under workload
Classifying performance issues by the discovery phase
- If we classify performance issues according to their
discovery time in the typical waterfall development process, we can
see the following main categories:
- Requirement issues, mainly related to a
missing or unrealistic service-level agreement
- Design issues, where the design is the
root cause of these issues
- Development issues, such as not
following best coding practices, or bad cod-
- ing quality
- Testing issues, such as missing or bad
quality performance testing
- Operational issues, which are mainly
related to production environment-
- specific issues, such as the database size or newly
introduced system, and so on
No comments:
Post a Comment