[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278298#comment-16278298
]
Knut Anders Hatlen commented on DERBY-6809:
-------------------------------------------
I haven't studied all the details of MergeInserter, but it looks like an
ArrayList might be safe to use there. This code probably predates the
introduction of ArrayList in Java, so Vector was the only alternative at the
time. We replaced some Vectors with more modern collections a while ago, but
that work focused on the synchronized collections that were performance
bottlenecks. I doubt that it will be possible to measure any performance impact
of a couple of synchronized operations per temporary file in a merge sort, but
it still might be good to change it. If nothing else, readers of the code won't
need to spend time figuring out why a synchronized collection is used.
> Java 1.8 feature use
> --------------------
>
> Key: DERBY-6809
> URL: https://issues.apache.org/jira/browse/DERBY-6809
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Affects Versions: 11.0.0.0
> Reporter: sagar
> Attachments: 2017-12-04-143613_1366x768_scrot.png
>
>
> Suggestion ...
> Is it possible to auto modify the existing source code using tools like
> Netbeans, and take advantage of the new features in JDK 1.8 for better
> multiuser performance and better utilization of current day multicore
> processors?
> Plainly put, can we have from 11.0 onwards a version of derby which takes
> advantage of the advancements and new features in java 1.8 ...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
