If you are running on Linux you can "store" the db in the special
/dev/shm device which is in fact a (shared) memory disk, access to this
device is really fast and you even don't waste any java heapspace. One
nice thing is, when you run out of memory it autmatically uses the
swapspace if I rember right.
Am 04.01.2012 18:42, schrieb [email protected]:
There was a suggestion some time ago about using a RAM disk as db
storage as an alternative to in-memory database. An advantage will be
that you should not worry about GC, but it will still be slower that a
plain in-memory db. Maybe, the nio stuff in H2 can alleviate that.
Otherwise.. the problem with hard questions is that they have no
obvious questions.
--
Vasile Rotaru
--
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.
--
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.
