[jbossts-issues] [JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into

[Mark Little (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Little updated JBTM-1340:
------------------------------


  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
                
> BeanPopulator overhead needs looking into
> -----------------------------------------
>
>                 Key: JBTM-1340
>                 URL: https://issues.jboss.org/browse/JBTM-1340
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Common
>    Affects Versions: 4.17.2
>         Environment: Mac OS 10.7
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>             Fix For: 5.0.0.Final
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira