db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cliff Evans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-646) In-memory backend storage support
Date Fri, 08 Jun 2007 08:56:27 GMT

    [ https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502724

Cliff Evans commented on DERBY-646:

I think people are under valuing this request as a useful tool in production code.  I'm currently
using H2 to implement a multi-threaded matching engine which takes a series of events and
matches aggregated information held in an in-memory database in real time.  The datasets never
get too large but the matching can be quite complex.  Being able to use the expressive power
of SQL without the overhead of pesisting the information to disk makes the matching process
very fast while providing all of the thread synchronisation required in a tried and tested
package.  My only problem with H2 is the granularity of its locking.  Table or nothing.  This
causes blocking as the tables are updated which an in-memory, row-locked version of Derby
would reduce considerably.  We're talking manna from heaven here.

Are there any plans to include this in the main release?

> In-memory backend storage support
> ---------------------------------
>                 Key: DERBY-646
>                 URL: https://issues.apache.org/jira/browse/DERBY-646
>             Project: Derby
>          Issue Type: New Feature
>          Components: Store
>         Environment: All
>            Reporter: Stephen Fitch
>         Attachments: derby-646-1a-raw-compiles.diff, derby-646-1a-raw-compiles.stat,
> To allow creation and modification of databases in-memory without requiring disk access
or space to store the database.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message