#Azure #DocumentDB vs SQL Azure performance comparison — Revised
THE STORY
#Azure #DocumentDB vs SQL Azure performance comparison — Revised
THE STORY
A while ago I wrote some code to compare the performance of Azure DocumentDb and SQL Azure and the conclusion was:
WAIT … BACKUP
In this post a while a go, I introduced the Azure DocumentDB and showed how you can connect to it, create documents there and read documents with queries.
In terms of SQL Azure there is nothing special involved and it works exactly how on-premise SQL Server works, and you can use ADO.NET, Entity Framework or any other technique that you might want to use for SQL Azure.
Then, I compared the performance on these two data stores and see which one will do better!
BUT I WAS WRONG
Turns out, I was not following the best practices for using Azure DocumentDB, and DocumentDB can work much faster if you code it right!
So, @arkramac made a PR and fixed the code issues.
Now, after merging those changes I ran the tests available in the project on Github again.
The following table shows the results:
One thing to note here is that these numbers are, the time spent on network lag (mostly) , plus the actual database call.
INSERT PERFORMANCE
So, looks like for insert operations, DocumentDb dominates for sure and SQL Azure cannot come even close!
READ PERFORMANCE
When comparing the read operation of a single document vs read of a single record from SQL Azure, DocumentDb performs slightly better.
Note: when you read one document from DocumentDb, everything you need will be there so there in the document you get back, and you don’t need any additional calls needed to get the complete data, but in case of SQL Azure, because of normalization and foreign keys, normally you will need additional calls to get that data or at least have SQL joins which will make the Read operation slower.
But looks like reading several documents from DocumentDB, is slightly slower that SQL Azure, and again we should remember in case of SQL Azure there will be SQL Joins involved in real projects that we didn’t consider here, which will slow down the SQL Azure results.
LATEST CODE
you can find the latest code and the tests in Github here:
Over all, I believe the winner is Azure Document DB.
ANYTHING ELSE?
The SQL Azure instance that I use in this sample is the Standard trier, and looks like the Premium tier is much faster than the Standard, and of course will cost you more.
Take a look at the below post on MSDN to compare the Standard and Premium tier of the SQL Azure: