Much to their dismay, some folks experience an actual degradation of performance when porting their n-tier application from Microsoft® Windows NT® Server/MTS to Microsoft Windows® 2000/COM+. By merely using the default settings and without making any changes to their code, the responsiveness of their application may unexpectedly decrease significantly. This can prompt one to ask, "Okay, I did not change a thing, and my application is now a dog, what in the world can I do now?"
Do not be disheartened. Realize that performance isolation is not a trivial task by any means. It is often a convoluted blend of experience, testing, data gathering, research, trial and error, investigational espionage, dedication, and a bit of black magic (not necessarily in that order!). In the highly complex and interwoven world of today's n-tier application, there are many factors that can affect responsiveness. And by fixing one problem, you may expose another weakness in your architecture, maybe not even associated with COM+!
|