Standardize processes by deploying a backlog to Azure Boards using a template.
The first two of these were introduced in the previous phases but the cloud adoption plan generator is new to the planning phase. This uses Azure DevOps to build a backlog of items that will align your cloud adoption efforts to a standardized process. The use of this asset is covered in more detail in the slide deck and the notes section of the slides.
Extra Content and verbose slides
As always there is a ton of additional content in the notes sections of most slides to help prep you in using the deck. The content of the slides is quite verbose, far more verbose than what I would typically build. I prefer to use slides as guide for a conversation to keep myself on course as well as the audience. I tend to go deep when answering questions and usually encourage questions live during a presentation so I can end up down a rabbit hole and the slides are a great tool to get the presentation back on topic and to ensure I cover all the material. So, feel free to reduce the content of the slides if it works better for you. Typically, I would have someone attend a couple of presentations along with me when presenting this content, so they got a feel for the content and the flow of the presentations as well as get more knowledge of the subject before doing it themselves since we don’t have that opportunity I have included more content so that anyone can feel comfortable presenting this content after reviewing the slides a few times.
Jason Read at CloudHarmony does a great job sorting through all of the different cloud computer offerings by vendors and then compares their performance in a like-to-like benchmark. This is no small task and most reports I have read comparing cloud compute do not do a good enough job of comparing similar services when conducting their performance tests. You can obtain a copy of the full report from here which is 100+ pages long.
Below are some the test results along with my own comments as well.
In the web server test Amazon EC2 was a little better than the rest of the competition. And in the database server test Rackspace was slightly better until the testing of large database servers where Azure’s new A9 server won out.
Web Server CPU Performance Test
Database Server CPU Performance Test
Web Server CPU Performance Variability Test
Database Server CPU Performance Variability Test
Also included in this test was CPU variability. In these multi-tenant, shared resource environments the performance over time can be a risk to a customers if that is the case this test should be taken into consideration as well as the other variable tests included in the report. For this test the lower the score the better, ideally you want the same performance over the life of the service.
In both tests Amazon had the best overall score across all server types. The changing CPU types as testing across different server types should be considered when looking at these two scores as well.
Disk Performance Testing
In these tests Amazon EC2 and Rackspace were consistently faster and more reliable. Since they are SSD based storage they should be faster and more consistent than the other services. DigitalOcean is also SSD based but their performance was not on par with the other SSD based services and also had the highest rate of variability. SoftLayer is not SSD based but their overall disk performance and consistency were very good. This could be from using SSD caching but no matter how they are doing it the performance speaks for itself. Microsoft Azure and Google do not offer SSD storage which is reflected in their testing.
Web Server Tests
Small Web Server Random Reads Test
Small Web Server Sequential Reads Test
Small Web Server Random Reads Variability Test
Small Web Server Sequential Reads Variability Test
Small Database Server Random Read Writes Test
Small Database Server Sequential Read Writes Test
Small Database Server Random Read Writes Variability Test
Small Database Server Sequential Read Writes Variability Test
Medium Web Server Random Reads Test
Medium Web Server Sequential Reads Test
Medium Web Server Random Reads Variability Test
Medium Web Server Sequential Reads Variability Test
Medium Database Server Random Read Writes Test
Medium Database Server Sequential Read Writes Test
Medium Database Server Random Read Writes Variability Test
Medium Database Server Sequential Read Writes Variability Test
Large Web Server Random Reads Test
Large Web Server Sequential Reads Test
Large Web Server Random Reads Variability Test
Large Web Server Sequential Reads Variability Test
Large Database Server Random Read Writes Test
Large Database Server Sequential Read Writes Test
Large Database Server Random Read Writes Variability Test
Large Database Server Sequential Read Writes Variability Test
Memory Performance
In these test they conduct them only on the database servers and because of Azure’s older hardware based on AMD CPU and MOBO they did not perform well until the large database server test where they are using the newer Intel Sandy Bridge based platform. Amazon and Google both perform well through all testing and outperformed the others. Newer hardware is always going to win in these types of tests and that is reflected here.
Small Database Server Memory Test
Medium Database Server Memory Test
Large Database Server Memory Test
External and Internal Network Performance
Network testing is always subjective and by testing cloud service providers networking throughput it just adds to the complexity of the configuration as some add additional ways to improve performance through different setups. Amazon, Google and Rackspace seem to provide higher throughput then Microsoft Azure, DigitalOcean and Softlayer. Also throughput by some vendors is limited depending on the size of the compute instance your purchase.
Uplink – Internal Network Throughput
Downlink – Internal Network Throughput
Internal Network Latency
External Network Latency
They also cover the value of each provider in their report which ultimately should be the deciding factor in choosing which cloud computing provider to use for your solution. After all there is no need to overspend on a service if you can accomplish everything you need with a cheaper solution.
