Transaction Performance

Transactions add overhead to applications; thus, you should carefully consider the performance implications of transactions and use them appropriately. This is not a recommendation to avoid transactions! We are simply encouraging you to understand how to use transactions in a way to give the best performance possible for your application. The first, and perhaps most obvious, point is that distributed transactions (often called XA transactions) require more overhead than local transactions. Thus, if your application can be written to properly use only a single resource, this will result in the best performance.[9]

[9] The application code will still use the J2EE transaction mechanisms, just one resource.

Application use ...

Get IBM WebSphere: Deployment and Advanced Configuration now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.