[
https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-646:
----------------------------------
Attachment: derby-646-3a-jmx_experiment.diff
Patch 3a is a JMX experiment (very poorly documented, not very well tested,
contains bad code). It provides two JMX attributes and one operation;
getDatabases, estimateSpaceUsage, and estimateSpaceUsage(String).
You can obtain a list of the databases stored in memory, get a space usage
estimate for all the databases or for a single database.
Is this something we should consider adding?
We could also allow for deleting databases through JMX, but then we have to do
authentication (plus authorization?).
> 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
> Affects Versions: 10.5.0.0
> Environment: All
> Reporter: Stephen Fitch
> Assignee: Kristian Waagan
> Fix For: 10.5.0.0
>
> 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-2b-vfmem_first_rev.diff,
> derby-646-3a-jmx_experiment.diff, 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.
