There was a statement made a number of years ago in an ISWG (Integration Services Working Group) meeting which, to summarize, said "Don’t worry about performance, we’ll take care of that". While that is probably going to be the epitaph of at least one person, I think it is time to set the record straight.
Worry about performance.
OK, now that we’ve gone 180 degrees it’s time to put some parameters around this.
- Don’t worry about things over which you have no control. The speed of a DCOM call is something you have no control over, neither is the time required to create a connection for a connection pool, the time required to retrieve session state, nor the time required to process an HTTP request.
- Do worry about things over which you do have control. While you can’t do anything about the speed of a DCOM call, you can control, to an extent, the number of DCOM calls that you make. Less chattiness is better. While you do not have control over the speed of the resources, you have control over how effectively you use those resources.
The UAT and Production environments into which your application will eventually move has a myriad of interconnected pieces that, together, create the environment in which your application will exist. While you cannot control those resources you control how you use them. <Al Gore> Ineffective use of resources and our unwavering dependency on technologies that produce greenhouse gases is threatening our livelihood and our very planet.</Al Gore> Ineffective use of resources in any ecosystem is bad, whether that ecosystem is our planet, or our clustered production environment. Infinite resources are not available and never will be, but effective use can be made of existing technology:
- Up until the late 1990’s the computers on board the Space Shuttle flight deck were Intel 8086 chips.
- The original Xbox had a 733MHz CPU with 64MB of memory and yet it could (still can) outperform peoples desktops.
- Mission critical systems have been designed with, when compared to modern technology, primitive means.
- The first spreadsheet I used, Visicalc, ran on a 1 MHz processor.
All of these examples show that you can make something run well in limited circumstance, but you have to want to.