We run an application, AMS 360, as our in-house agency management application. The company who programs it is very vocal about how the product does NOT run well in a virtualized environment. Still, the benefits to virtualized consolidated backups are a no-brainer and we will not be traveling as advised...
True to their word, I installed the application (Two Parts: IIS server and DB back-end) and it is, for lack of better words, sludgy. Hopefully one of the experts has experience troubleshooting web front end/sql DB applications contention. I've googled and haven't found any ground breaking information.
I don't think it's hardware contention by any means. The guest can r/w 800MB/s, It has 16GB memory (I've tested with 24), 8 cores (which remain bored throughout the day, even though affinity is set corretly) and the DB is around 120GB. The users access the application through an identical 2008R2 TS.
There's got to be some VMWARE setting I've overlooked or not read about that is causing the application to stick. Is there some IIS compression or caching I could enable? Some caveat I don't know about as far as best practices with IIS or SQL that is commonly overlooked? I'm at your mercy. Please help.