Skip to main content

Azure VMs with SSD are now available - Benchmark using MongoDB over SSD

Today, Azure team announced that we will have VMs with Solid State Drives. Wow, this is so cool.
Why this is so great? Well, first of all, if you work with application that have a high demand of I/O on disk than this could be the perfect solution for you. Of course, the new machines has a new configuration, with additional processing power, but I don’t want to talk about this.
For more information related to this VMs you can go to:


In this blog post we will focus on the new SSD that are coming on this machines. Based on the configuration, the new D-Series machines are coming with local SSD that start from 50GB and goes to 800GB.
It is pretty interesting to put a MongoDB server on this partitions or other intensive I/O application. Also, if you have SQL Server on a VMs, you can put BPE (Buffer Pool Extension) on that partition. Don’t forget that BPE can be activated very easy and can increase the performances of SQL Queries. I expect a performance improvement of this kind of applications.
An important thing that you need to keep in mind. This SSD drives are only available for the TEMP drive. The operating system will still run on a classic drive. In future we may see other parts of VMs running on SSD, but is only a dream.
Additional to this, because we are in the TEMP driver (and we are using a SSD), you should add only data that you can afford to loss.
Benchmarks
I found an interesting benchmark related to Microsoft Azure VMs that I think that could be interesting for us:

  • A1 VM (1 core, 1.75GB RAM) Score: 2703
  • D1 VM (1 core, 3.5GB RAM) Score: 3947
  • A4 VM (8 cores, 14GB RAM) Score: 8705
  • A8 VM (8 cores, 56GB RAM) Score: 17186
  • D4 VM (8 cores, 28GB RAM) Score: 12645
  • A9 VM (16 cores, 112GB RAM) Score: 29873
  • D14 VM (8 cores, 112GB RAM) Score: 22017 

MongoDB Load Test
Because in the last period of time I had the opportunity to play a lot with MongoDB, I had the setup of a load test for MongoDB. Nothing special, around 30M objects in one table. I only execute read operations over MongoDB, without any writes over it.
I run this load test 20 times on this machine, each time making a full restart of the machine. 10 times I had the database in the temp folder (SSD support) and 10 times in a normal folder (standard hard disk).
The results were pretty interesting, from my perspective. SSD disk improved with around 2.5X the performance of MongoDB queries. The result time is not very relevant, but the average execution time reduced from ~30ms per query to around ~13ms per query.
Take into account that SSD are not so fast when we need to make an insert or update. Because of this I didn’t even wanted to do a test like that. I don’t like the ideas to store content in a directory where I can loss all the information (like TEMP), but using a replica you can resolve this issues (but the performance will be lower).
Conclusion
There are scenarios when a SSD can help you a lot when you need to improve your performance, especially when you need to make a lot of I/O operations (especially read). I like the idea to have VMs with this kind of configuration and I expect to use them in the near future.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...