Skip to main content

(Part 2) Testing the limits of Windows Azure Service Bus


In one of my last post we talked about the performance of Windows Azure Service Bus and what is the maximum number of messages that we could process in a given period of time.
In this post we will see what is the maximum numbers of consumers that we can have for subscription on Service Bus. Before staring, you should know that this refers directly to our own requirements and with our custom actions that we need to do for each message. Because of this, for each kind of application, the result can vary a lot.
Scope:
To see what is the “magic” number of Windows Azure Worker Roles instances that we can have on cloud that can process messages from only one topic.
Environment:
Each message that was added to Service Bus was pretty small. We had around 100 characters in UTF7 and 3 properties added to each BrokeredMessage.
We run the tests with one; two and three subscribers with different filter rules and the result were similar.
Each message that is received from Service Bus required a custom action to be executed. This action is pretty complicated and consumes CPU power. Also the logic requires to access remote services (that are stored in the same data-center).
Action:
First step was to use only one instance that consumes messages. We tried to determine what kind of instance is more suitable for us – from CPU perspective and number of messages that are processed. We tried the size of the instance type that offers us the best price per instance also.
Remarks: The processer level of each instance was at around 80-85%. We use an automatic scaling mechanism over threads that take into account the CPU power, number of processors and so on. During the tests, there were client that produces messages in the same time – this was required because we had to see how Service Bus behave in a real situation, not in a situation when topic already contains all the messages
Second step was to identify the size of instance that was most suitable for us from all perspective. The cost was one of the most important one. After this we scale from 1 to n instance to identity where what is the maximum number of instances that we can have.
Results:
After first step we identify that 100.000 messages can be processed by roles in the following time:

  • Small – ~19 minutes
  • Medium – ~18 minutes
  • Large – ~18 minutes
  • Extra large – ~17 minutes

The best performance related to costs was offered by the Medium size instances.
Next step was to see what is the processing time of 100.000 messages using different number of instances. All the instances that were used at this step is Medium. We end up with the following times:

  • 1 instance – 18 minutes
  • 2 instances – 11 minutes 
  • 3 instances – 7 minutes
  • 4 instances - 4 minutes
  • 5 instances – 3 minutes
  • 6 instances – 2 minutes
  • 7 instances – 2 minutes
  • 8 instances - 2 minutes

In our case we observed that the number of instances that would make us happy and the cost would be pretty okay also is around 4 instances.
Costs:
The costs for processing 1.000.000 messages are pretty good:  4 x 0.16$ + 1$ = 1.64$.
Conclusion:
In this post we saw what is the size of the worker role that is most suitable for us. Using a Medium size worker role will offer us the best performance, reported to price. In the next post we will take a look over the duration of processing different number of messages using Medium size instances and differet number of instances.

Comments

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 http://go.microsoft.com/fwlink/?LinkId=260882 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 …

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…

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.
publ…