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.
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).
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.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…