[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566050#comment-14566050
]
Mike Matrigali commented on DERBY-6809:
---------------------------------------
Some generic comments on possible improvements in the sorted not specific to
java 1.8 feature use.
The sorter is an area of the system that should be easy for a new derby
developer to contribute to. The current base implementation
has changed very little than what was put together for the initial release of
the closed source Cloudscape system. All the code is
localized in java/engine/org/apache/derby/impl/store/access/sort.
Sort is used mainly for 2 things in derby: index creation and SQL order by.
Hardly any work has been done on improving index creation performance, not many
requests. Some number of apps create indexes
when table is empty so sort not an issue. Other percentage of derby use has
relatively small tables so again not an issue.
For order by performance most problem queries are better served by sort
avoidance (by having the right indexes) rather than improved order by.
Even though not a lot of work has been done, I do believe there is room for
improvement. Probably easiest would be to get community to agree to update
the default sort size, and probably at same time provide a documented knob so
that if that broke old applications one could dial it back. Current code
attempts
to keep memory usage around 1 meg per sort.
An interesting first step might be to just provide an implementation of sort
that uses modern jvm collections (which did not exist when code was first
implemented) and compare to the hand coded sort implementation.
> 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
>
> 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.3.4#6332)
