[
https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-646:
---------------------------------
As to how to proceed, first is there an icla for cheng's contribution?
Is it possible for either of these patches to run through the entire derby test
suite, in in-memory mode?
how does either compare to "test mode" with the page cache set as big as
expected in-memory
use?
Kristian, or any other committer, can you take a look at both implementations
and comment
on any
strength's/weeknesses from both. As you suggest it would be nice if we could
get a combined
agreed implementation from both.
If goal is really the fast approaching 10.5, then it would be nice to have some
sort of upper level user documentation. How to use it, what are limits, is all
functionality supported. What happens in case it runs out of memory, or
internal limits.
> 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, derby-646-20090222.diff,
> derby-646-20090222.stat, derby-646-2a-vfmem_first_rev.diff,
> derby-646-2a-vfmem_first_rev.stat, derby-646-performance_comparison_1a.txt,
> svn.diff
>
>
> 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.
