Batching Messages in a Transaction

Batching Messages in a Transaction


Queued applications use transactions to ensure correctness and reliable delivery of messages. Transactions, however, are expensive operations and can dramatically reduce message throughput. One way to improve message throughput is to have an application read and process multiple messages within a single transaction. The trade-off is between performance and recovery: as the number of messages in a batch increases, so does the amount of recovery work that required if transactions are rolled back. It is important to note the difference between batching messages in a transaction and sessions. A session is a grouping of related messages that are processed by a single application and committed as a single unit. Sessions are generally used when a group of related messages must be processed together. An example of this is an online shopping Web site. Batches are used to process multiple, unrelated messages in a way that increases message throughput. For more information about sessions, see Grouping Queued Messages in a Session. Messages in a batch are also processed by a single application and committed as a single unit, but there may be no relationship between the messages in the batch. Batching messages in a transaction is an optimization that does not change how the application runs.

The TransactedBatchingBehavior endpoint behavior controls batching. Adding this endpoint behavior to a service endpoint tells Windows Communication Foundation (WCF) to batch messages in a transaction. Not all messages require a transaction, so only messages that require a transaction are placed in a batch, and only messages sent from operations marked with TransactionScopeRequired = true and TransactionAutoComplete = true are considered for a batch. If all operations on the service contract are marked with TransactionScopeRequired = false and TransactionAutoComplete = false, then batching mode is never entered.

A batched transaction is committed based on the following:

  • MaxBatchSize. A property of the TransactedBatchingBehavior behavior. This property determines the maximum number of messages that are placed into a batch. When this number is reached, the batch is committed. This is value is not a strict limit, it is possible to commit a batch before receiving this number of messages.

  • Transaction Timeout. After 80 percent of the transaction's time-out has elapsed, the batch is committed and a new batch is created. This means that if 20 percent or less of the time given for a transaction to complete remains, the batch is committed.

  • TransactionScopeRequired. When processing a batch of messages, if WCF finds one that has TransactionScopeRequired = false, it commits the batch and reopens a new batch on receipt of the first message with TransactionScopeRequired = true and TransactionAutoComplete = true.

  • If no more messages exist in the queue, then the current batch is committed, even if the MaxBatchSize has not been reached or 80 percent of the transaction's time-out has not elapsed.

If a message in a batch causes the transaction to abort, the following steps occur:

  1. The entire batch of messages is rolled back.

  2. Messages are read one at a time until the number of messages read exceeds twice the maximum batch size.

  3. Batch mode is re-entered.

The size of a batch is application-dependent. The empirical method is the best way to arrive at an optimal batch size for the application. It is important to remember when choosing a batch size to choose the size according to your application's actual deployment model. For example, when deploying the application, if you need an SQL server on a remote machine and a transaction that spans the queue and the SQL server, then the batch size is best determined by running this exact configuration.

To increase throughput, you can also have many batches run concurrently. By setting ConcurrencyMode.Multiple in ServiceBehaviorAttribute, you enable concurrent batching.

Service throttling is a service behavior that is used to indicate how many maximum concurrent calls can be made on the service. When used with batching, this is interpreted as how many concurrent batches can be run. If the service throttling is not set, WCF defaults the maximum concurrent calls to 16. Thus, if batching behavior were added by default, a maximum of 16 batches can be active at the same time. It is best to tune the service throttling and batching based on your capacity. For example, if the queue has 100 messages and a batch of 20 is desired, having the maximum concurrent calls set to 16 is not useful because, depending on throughput, 16 transactions could be active, similar to not having batching turned on. Therefore, when fine-tuning for performance, either do not have concurrent batching or have concurrent batching with the correct service throttle size.

An endpoint is composed of an address and a contract. There may be multiple endpoints that share the same binding. It is possible for two endpoints to share the same binding and listen Uniform Resource Identifier (URI), or queue address. If two endpoints are reading from the same queue, and transacted batching behavior is added to both endpoints, a conflict in the batch sizes specified could arise. This is resolved by implementing batching using the minimal batch size specified between the two transacted batching behaviors. In this scenario, if one of the endpoints does not specify transacted batching, then both endpoints would not use batching.

The following example shows how to specify the TransactedBatchingBehavior in a configuration file.

        <behavior name="TransactedBatchingBehavior"

The following example shows how to specify the TransactedBatchingBehavior in code.

using (ServiceHost serviceHost = new ServiceHost(typeof(OrderProcessorService)))
     ServiceEndpoint sep = ServiceHost.AddServiceEndpoint(typeof(IOrderProcessor), new NetMsmqBinding(), "net.msmq://localhost/private/ServiceModelSamplesTransacted");
                sep.Behaviors.Add(new TransactedBatchingBehavior(100));

     // Open the ServiceHost to create listeners and start listening for messages.

    // The service can now be accessed.
    Console.WriteLine("The service is ready.");
    Console.WriteLine("Press <ENTER> to terminate service.");

   // Close the ServiceHostB to shut down the service.
© 2016 Microsoft