[
https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin....
]
Mark Little commented on JBTM-2180:
-----------------------------------
Yes. I know BasicAction uses Hashtable for maintaining child thread and actions, but since
concurrent threads in the same transaction or nested transactions aren't used much,
this may not be a problem there. StateManager's use of Hashtable may be a different
matter though, since StateManager is used everywhere.
However, having a good analysis of the overhead is definitely the right first step. Then
at least if we make no changes we can do so based on facts and not supposition. Also
precisely which collections framework we might use were it to be necessary, is a job in
its own right :-)
Determine whether or not we should use a specific collections
framework
-----------------------------------------------------------------------
Key: JBTM-2180
URL:
https://issues.jboss.org/browse/JBTM-2180
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JTA, JTS, Performance Testing, REST, Transaction Core
Affects Versions: 5.0.1
Reporter: Mark Little
Assignee: Michael Musgrove
We use many of the inbuilt collections implementations (such as Hashtable) which are well
known to be suboptimal in certain cases. Should we use a separate collections framework,
e.g.,
https://github.com/goldmansachs/gs-collections
There are pros and cons of doing this. But first we need to determine whether it really
makes sense from a performance perspective.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)