Another thing i can highly recommend is to do a performance baseline check for your solution before you start installing any custom code or third party products, for both your test/integration servers and preprod/prod environments.
After each deploy you do another benchmark and compare it to your baseline.
This will help you alot when you start developing functionality that, inevitably, will slow down your system. That way you can catch "bad deploys" very early.
Theres different approaches and tools for this. Stress test in Visual Studio Test Edition is one way, but a simple load test tool like WCAT or similar could also give a good indication of degrading performance that hints that a badly performing assembly was deployed.