Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-13864

Improve performance by configuring read-only transactions on more Spring proxies

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      There's a few places where we can indicate read-only transactions to the Spring transaction wrappers. This removes the need for Hibernate to do a dirty check as part of it's "flush-if-necessary" check at the end of the transaction interceptor and improves performance.

      Specifically, the following should be read-only:

      • DAO transaction interceptor, get* methods
      • PermissionManager interceptor, has* methods
      • Plugin transaction interceptor, get* methods.

      Additionally, get* methods on UserAccessor can be read-only except for ones that access property sets.

            matt@atlassian.com Matt Ryall
            matt@atlassian.com Matt Ryall
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: