Performance I just don’t understand Win 2008 vs Win 2012 on AWS

After having some weird connection issues over the last week since migrating my blog and portfolio to an alternative configuration instance based on Windows Server 2008 I decided to do a load test to see whether this was a bigger issue than I expected. The results I just cant explain.

 

Windows Server 2008, IIS Installed only with .NET4

AWS_Win2008_Performance

 

Windows Server 2012, IIS Installed only with .NET4

AWS_Win2012_Performance

 

As can be seen from the 2008 graph the server fell over very quickly and took a very long time to recover. After looking at this went to the CPU load and found the answer:

Windows Server 2008, IIS Installed only with .NET4

AWS_Win2008_CPULoad

Windows Server 2012, IIS Installed only with .NET4

AWS_Win2012_CPULoad

 

This wasn’t the profile of the CPU when I first set up the instance, I have no idea what has caused the development of this maxed CPU issue. Will have to look into more, but for the moment am back on 2012! Does demonstrate the importance of setting up alarms though, another nice functionality on the AWS platform.

 

Edit:

Maximum Load Test

I have also done a max load test just to see how much the server could take, maxes out about 70 users. Tested against blog, so all img,js and css are additional calls wrapped into one user call. Granted when server hits max capacity is essentially unresponsive.

AWS_Win2012_Max_Performance

Saturday, January 26, 2013 3:36:47 PM Categories: Amazon Evaluation Microsoft Tech
Stuart James