>[4] Can we persist to disk the contents in an OffHeapStore (take a 
snapshot to disk and then reload it when the app restarts)?

I think [4] has a pretty simple implementation.  When a user wants to save 
to disk, just create a temporary FileStore, and copy all the key-values 
from the Off-Heap-Store into the FileStore map(s), and the commit and close.

This could be built into to the OffHeapStore as a function: public void 
saveToFile(fileName), and a corresponding loadFromFile(fileName) that does 
the reverse.  But it could just as easily be done by the applilcation 
programmer instead of being built into the OffHeapStore class.

-Adam



On Monday, October 17, 2016 at 7:27:43 PM UTC-4, Adam McMahon wrote:
>
> Hi,
>
> I am a long time user of H2, but I am now just exploring the MVstore map 
> api.   Great stuff, a few questions:
>
> [1]  Off heap storage - is there any way to designate the size of the 
> offheap store, or does it just continue to fill up until it runs out of 
> memory?
>
> [2]  Off heap storage - Can we  designate how much of the map should be in 
> heap vs offheap?
>
> [3] Can the Off heap storage be used in conjunction with an overflow file 
> storage (for example, if so much memory is used it overflows to a file?
>
> [4] Can we persist to disk the contents in an OffHeapStore (take a 
> snapshot to disk and then reload it when the app restarts)?
>
> Best,
>
> -Adam
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Reply via email to