[
https://issues.apache.org/jira/browse/TAP5-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100729#comment-13100729
]
Hudson commented on TAP5-1638:
------------------------------
Integrated in tapestry-trunk-freestyle #509 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/509/])
TAP5-1638: Remove use of ConcurrentBarrier inside AbstractMessages, replace
with ConcurrentHashMap
TAP5-1638: Reduce thread contention inside ComponentClassResolverImpl
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166911
Files :
*
/tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/util/AbstractMessages.java
*
/tapestry/tapestry5/trunk/tapestry-ioc/src/test/java/org/apache/tapestry5/ioc/internal/util/MessagesImplTest.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166906
Files :
*
/tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ComponentClassResolverImpl.java
> Reduce thread contention inside ComponentClassResolverImpl
> ----------------------------------------------------------
>
> Key: TAP5-1638
> URL: https://issues.apache.org/jira/browse/TAP5-1638
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Labels: performance
>
> There is looking to be a fair amount of thread lock contention inside
> ComponentClassResolverImpl; use of ConcurrentBarrier appears to not be
> sufficient (or poorly tuned).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
