Bottlenecks are the parts of the system that limit performance. The system is made up of multiple parts that can run in parallel, for example the disk can be doing disk IO at the same time as the CPU is running some code, but when the system is at its maximum throughput then one of [...]
Monthly Archives: April 2008
MarkJ’s Rules of Good Software Performance
April 21, 2008 – 12:21 am
To get good performance from your software applications, developers, architects, and project managers need to follow MarkJ’s Rules of Good Software Performance:
1) Measure first and optimize second - find bottlenecks , ie don’t guess where a performance problem might be before you have one, find the slow part of the system through testing and make [...]
Scalability and Other Meanings of Performance
April 17, 2008 – 3:21 am
In Throughput and Response Time I described the essence of what we mean by software performance, but there are some additional meanings that are important to consider in many cases. So here is a bigger list of what we mean when we talk about performance:
Response Time
Throughput
Scalability
Stability
Resource Utilization, eg memory footprint
Overload or failure characteristics
Capacity planning
So lets [...]
Throughput and response time
April 16, 2008 – 8:25 am
What does ‘performance’ mean? Software performance is mostly about how fast the software goes and how much work it can handle. To discuss performance we need more accurate terms than ‘speed’. The two most important concepts are:
Response time - how quickly the system responds to request
Throughput - how much work can it do in some [...]