Hello everyone. Congratulations to the developer team for this excellent product.
After a lot of research H2 looks like the database my company needs for our current project. I would preciate your help with a few questions: 1. We are building a high-performance, data-intensive solution. So we need to use the in-memory mode, copying the data from another database and keeping it in the same JVM as the code. Unfortunately, the copy process itself will take a long time, so in addition to keep data in- memory we need it to persist on disk, so if the system goes down we won't need to copy it all from zero. Keep in mind it isn't about caching, since we need data available on memory as soon as the service is up and running. Perhaps it's something one would call a proactive cache, meaning a cache which is loaded before any client request data. How do we achieve to keep the data in memory but also persist it to disk, and have it auto-loaded to memory after a H2 restart? If there is no built-in way, any workaround? 2. When we use the in-memory mode: 2.1 Where do I set the max amount of memory it will use? 2.2 Is the memory shared with the other processes on the JVM, or H2 "grabs" his part from the startup? 2.3 How can I know how much of the H2 memory is still free? 2.4 What happens when the assigned memory is full (discard data, OutOfMemoryError, another...)? 2.5 Can I set up a parameter in order to whenever the memory gets full the rest of data go to disk? Thank's in advance. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
