[
https://issues.apache.org/jira/browse/DERBY-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen closed DERBY-698.
------------------------------------
Resolution: Fixed
I'm closing this issue as fixed (with no particular fix version specified)
since many fixes to utilize java.util.concurrent classes have gone into Derby
over time, solving the most pressing issues found when profiling Derby on CMT
machines. See for example the issues linked from this issue. There may be more
places where we could use them, but in that case we should file more specific
JIRA issues and track each of them separately.
> Use Java 5 concurrent collections for better concurrency (rather than
> synchronized collections)
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-698
> URL: https://issues.apache.org/jira/browse/DERBY-698
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Reporter: David Van Couvering
>
> The new Java 5 concurrency utilities includes a set of concurrent collections
> that allow for greater concurrency than the current synchronized collections
> we are using. This could provide performance improvements for Derby,
> particularly in CMT (chip multi-threading) architectures.
> See
> http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/package-summary.html
--
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
