Skip to main content

SQL 2012 AlwaysOn: Synchronous vs. Asynchronous commit. Performance impact

Recently I've had a chance to build a 3-server AlwaysOn environment distributed between the primary and secondary data centers.

The configuration looks like this:

Primary Data Center                         Secondary Data Center              
         SQLDEV1                                        SQLDEV3
         SQLDEV2


The availability group was crated with synchronous commit replicas on SQLDEV1 and SQLDEV2 and the replica on SQLDEV3 was configured for asynchronous commit.

The link between the data centers was not great and when I pinged SQLDEV3 from SQLDEV1 I got these results


Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 63ms, Average = 42ms


I also created a very simple application that:
- generates a random INT
- if the table has a record with such key its updates the record otherwise it adds a new record to the table.
- every 5 seconds the app also records to a different (result) table StartTime, EndTime, and total number of inserts/updates

And I query the result table and sum up totals updates occurred in past 10 seconds.

I executed this application with 4 concurrent users from SQLDEV1 and the test database was also hosted on the same server.

Then the test database was not a part of the availability group the average number of transaction per second was 5,500-6,000.

When the test database was a part of the availability group with synchronous commit to SQLDEV2 and asynchronous commit to SQLDEV3 the average number of the transactions was 2,800 - 3,300

And in the final test I changed the replica on SQLDEV3 to by in the synchronous-commit mode. And the average number of the transactions dropped to 40-60 per second (yes, decrease of two orders of magnitudes).

Certainly, this is not a valid performance  tests but nevertheless it gives some feeling of the performace impact ones can expect when dealing with AlwaysOn.






Comments

  1. would you be able share the tool you created for your test? Also, how did you measure transactions per second? I am working on a similar test myself.

    ReplyDelete
    Replies
    1. Hi Dustin,

      I've posted the script here

      http://smizrohi.blogspot.ca/2013/04/a-simple-script-to-test-server.html

      Let me know if it works for you

      Regards,
      Serguei

      Delete
  2. Your new valuable key points imply much a person like me and extremely more to my office workers. With thanks; from every one of us.
    Amazon Web Services Online Training

    ReplyDelete
  3. Thank you for your post. This is excellent information. It is amazing and wonderful to visit your site. This article is very much helpful and i hope this will be an useful information for the needed one.Keep on updating these kinds of informative things.
    oracle training in chennai

    oracle training institute in chennai

    oracle training in bangalore

    oracle training in hyderabad

    oracle training

    oracle online training

    hadoop training in chennai

    hadoop training in bangalore





    ReplyDelete

Post a Comment

Popular posts from this blog

SQL 2014 performance - Local disk vs. Azure Blob vs. Azure VM attached disk

Today I decided to compare SQL 2014 (RTM) performance when running a test against  - a local database (created on  WD7500BPKT - 750 GB 7200 RPM)  - a DB created on a disk attached to the A3 (3 cores, 7 GB) VM in Azure - a DB created on an Azure blob The VM in Azure was created in the US East region using the SQL 2014 template from the gallary provided by Microsoft. All databases were created with a single 10 GB data file (10 GB) and 1GB  log file. On the local SQL instance the DB was created as CREATE DATABASE TestDBonLocal ON     (NAME = file_data1, FILENAME = 'C:\TEMP\filedata1.mdf', SIZE = 10GB, FILEGROWTH = 256 MB )  LOG ON  (NAME = file_log1, FILENAME = 'C:\TEMP\filelog1.ldf', SIZE = 1GB, FILEGROWTH = 32 MB)  On the Azure VM the database on the attached disk (the disk was mapped as drive F:) was created as such CREATE DATABASE TestDBonDisk ON     (NAME = file_data1, FILENAME = 'F:\TMP\filedat...

Create 3-Node Windows 2012 Multi-subnet Cluster

Environment There are two Data centers connected via a WAN link. Two Windows 2012 Servers (called SQLDEV1 and SQLDEV2) are located in the Primary Data Center (on the IP subnet 192.168.79.0/24) and the third server is placed in the Secondary Data Center with the 192.168.69.0/24 subnet. We’ll be creating a three-node Windows cluster with no shared storage on the multi subnet network with a file share witness at the Primary Data Center. We’ll be using a file share witness to protect from the cluster failure in a situation when the network between the Data Centers is unavailable and one of the servers in the Primary Data Center is also down (or being rebooted). The final state will look like depicted above: -           Two Virtual IP’s will be assigned (192.168.76.218 and 192.168.69.134) to the cluster -           The servers at the Primary Data Center will have a vote (Vote=1) and the ...