Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-1340

BeanPopulator overhead needs looking into

    XMLWordPrintable

Details

    • Enhancement
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Out of Date
    • 4.17.2
    • 5.2.6.Final
    • Common
    • None

    Description

      During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit.

      6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled
      6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean
      6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance
      6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance
      2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder.<init>
      2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString
      0.0% - 320 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey
      0.0% - 61 µs - 10,000 inv. java.lang.Class.getName
      0.0% - 25 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.get

      Attachments

        1. Call_Tree.html
          21 kB
        2. Hot_Spots.html
          13 kB
        3. SpeedTest.java
          5 kB

        Issue Links

          Activity

            People

              thjenkin@redhat.com Tom Jenkinson
              nmcl2001 Mark Little
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: