I thought I'd create this thread for the benefit of anyone that thinks tuning isn't necessary in todays world with so much CPU power on tap.
I work for a large company who has just had a new system developed, like any new system there have been a few teething problems and one of the users' main gripes was the speed (or lack of it) of the new application.
So, we looked on the database and the UNIX box on which the database was running and saw the problem.
We don't exactly have an underpowered box for this thing (16 x 1.2 GHz UltraSparc IVs with 64Gb of RAM) but we were seeing that it was completely maxed out during working hours.
A quick look on the database showed that during the 8 hours of a working day in April there were 5.6 billion logical reads
Obviously there was a concerted effort to tune as much code as possible and the last of the current phase went in yesterday.
Now we are showing only 1.6 billion reads in the same time period, much more CPU free and some much happier users.
Next time someone says that you don't have to bother making things efficient nowadays I'd take the advice with a pinch of salt!
I work for a large company who has just had a new system developed, like any new system there have been a few teething problems and one of the users' main gripes was the speed (or lack of it) of the new application.
So, we looked on the database and the UNIX box on which the database was running and saw the problem.
We don't exactly have an underpowered box for this thing (16 x 1.2 GHz UltraSparc IVs with 64Gb of RAM) but we were seeing that it was completely maxed out during working hours.
A quick look on the database showed that during the 8 hours of a working day in April there were 5.6 billion logical reads

Obviously there was a concerted effort to tune as much code as possible and the last of the current phase went in yesterday.
Now we are showing only 1.6 billion reads in the same time period, much more CPU free and some much happier users.
Next time someone says that you don't have to bother making things efficient nowadays I'd take the advice with a pinch of salt!