db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sagar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6809) Java 1.8 feature use
Date Sat, 30 May 2015 16:58:17 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566097#comment-14566097
] 

sagar commented on DERBY-6809:
------------------------------

And finally though derby is popular mostly as an embedded database or an in memory database
.... most of my thinking is oriented toward derby as a network client server traditional database.
Dunno if thats right

And hence the thought of using the multicore improvements and full support in the new Java8
so that better performance is achieved when there are 100s or even thousands of concurrent
users via a webapp using a connection pool ...







> 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)

Mime
View raw message