Have a look at this video clip before we get into the concept of understanding performance.
Fiat Bravo vs. Ferrari 550 Maranello vs. Ferrari F1
The three cars in this video are clearly very different. For a formula one car the objective is easy to define. “Get around the track as fast as possible while meeting all FIA regulations and maintaining appropriate (two race) reliability of every component.”
For a Ferraro F550 it is a little more difficult to define. Probably somerhing like “Meet super-luxury standards and reliability for a road going sports car while offering super-car performance at a super-car price-point.”
For the fiat it is more likely “provide basic mass producable budget transportation”
Based on their specific goals it is obvious that we would define performance slightly differently.
For the F1 car it is about winning the constructors championship. For the GT car it is being recognized as the best luxury sports car. For the fiat it is about sales and market share in the budget category.
The point is that for three products produced by the same organisation the goals are completely different and the performance goals are consequently completely different as well.
The key is understanding your goals, understanding how you could measure success, and then target optimizing those metrics.
My view is that architecting for performance starts here. It isn’t a one- time thing either. This is why monitoring is key.
I will be speaking at an Enterprise IT Architecture Conference on the 28th and 29th of July 2008.
Attached are my Presentation Notes that I will talk to on the topic of Architecting for Performance and IT Asset Management
The videos used in the Performance Presentation are:
Fiat vs Ferrari F550 vs Ferrari F1
F1 Safety Focus – Telemetry
Alonso in McLaren vs 3 Mercedes
At IBM’s headquarters, a contribution to cost saving is to shut down the catering services in all but one building from Friday mornings.
This means that someone wanting a cup of coffee would have to walk 10 minutes to the central building in order to get a cup of coffee.
So a 20m break for each cup of coffee. Now a few techies I know have up to 8 cups of coffee in a day. Some software developers seem to be entirely fueled by coffee. How will this end? Are developers no longer being fueled by coffee? Or is this just a mistake?
Allow me a small rant if you would.
I tried to upgrade my data contract with my cellular service provider today. Ughhhzzz. I use a month-to-month service because I want to be able to switch providers should there be a price restructuring in South Africa. The bandwidth market is grossly overpriced here and we have seen several downward price adjustments in the last few years as a result of international competition.
Now all the service providers have month-to-month voice offerings, but vodacom does not have a monthly data product and Virgin does not have 3G, so for data I am with MTN. This month, I needed more than my 2gig bundle and wanted to add another 2gig. Guess what? It cannot be done. How insane is that? Here is a good customer who has exceeded his usage of your product and wants to buy more and you say sorry we cannot sell you any more unless you are prepared to pay 5 times more for the additional quantity. Wow! You would think selling a larger quantity to an existing customer would be something a company would like to do. Not so MTN. Clearly their pricing structure encorages people to buy LESS of their product. This must be some innovation in marketing that we did not cover at business school.