Sync Group - Let's talk about Performance

In one of my latest post I talked about synchronization functionality that is available for SQL Azure. There was a question related of the performance of this service.

So, I decided to make a performance test, to see what are the performance. Please take into account that this service is in the preview and the performance will change when the service will be released.

For this test I had the following setup:

Database

Size 7.2 GB
15 tables
2 tables with more than 30.000.000 of rows (one table had around 3.2 GB and the other one had 2.7 GB)
34.378.980 rows in total

Database instances

1 DB in West Europe (Hub)
1 DB in West Europe
1 DB in North Europe
1 DB in North Central US

Agent

1 agent in West Europe

Configuration

Hubs win
Sync From Hub

Scenario One: Initialize Setup

I started from the presumption that your data were not duplicated yet on all the databases. First hit of the Sync button will duplicate the database schema of the tables that needs to be sync, table content and rest of resources to all the databases for the given table. This means that 7.2 GB were send to the 3 different databases.

Normally you can do this action in other ways. Exporting/Importing the database for example, but I wanted to see how long it takes to sync all the databases.

Sync action duration: 5 hours and 36 minutes (20160.17 seconds)

Scenario Two: Update 182 rows

In this scenario I updated 182 rows from one of the tables

Sync action duration: 53.63 seconds

Scenario Three: No changes

In this case I triggered the synchronization action without any changes.

Sync action duration: 38.47 seconds

Scenario Four: 23.767 rows updated

23767 rows were updated on the hub database.

Sync action duration: 1 minute and 16 seconds (76 seconds)

Scenario Five: 4.365.513 rows updated

As in the previous scenario, I updated I changed a specific number of rows.

Sync action duration: 1 minute and 41 seconds (101.6 seconds)

Scenario Six: 76.353 rows deleted

From one of the tables I deleted 73.353 rows.

Sync action duration: 56.26 seconds

As we can see, the synchronization action itself takes a very short period of time. For 4.5M of rows that were updated, the synchronization action took less than 2 minutes. The only scenario that took a log period of time was the initial synchronization action. Usually this action is made only one time. Also we have other method to import the database content to all our database.

I would say that the performance of the sync service is very good and I invite all of you tot check it out. You have support for synchronization out of the box.

Great job!

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users. This information might be useful in the future when we need to decide where we want to keep and manage our users. Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

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.51 EF 6.0.2 VS2013 It see

Cloud as a Story - Vunvulea Radu

Search This Blog