db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-646) In-memory backend storage support
Date Tue, 17 Feb 2009 11:07:00 GMT

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

Kristian Waagan commented on DERBY-646:

Yes, me too. However, since I was interested in learning a bit more about Derby and because
I didn't know the state of the existing patch, I started from scratch.
It is my impression that the existing patch isn't "production ready".

I think it would be cool to compare our approaches. Maybe we can draw from both of them and
create an even better solution!
The only thing my prototype leaves on disk, is derby.log. I think this can be easily changed,
but often you would want to consult the log anyway.
The goal of my implementation is to avoid creating files/dirs on disk, which for some people
is attractive for running tests. I believe there are also performance benefits, especially
for update operations, at the cost of increased memory usage of course. The database creation
time should also be shorter, but I haven't obtained any numbers on this yet.

> 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