yes. I saw that in the docs. What I'm interested in is your design goals for the feature....what are you trying to accomplish? I'm going to be using an embedded, in-memory db that is concurrently accessed from multiple threads. Ultimately, "which mode should I use?" is the question. What are the costs and benefits to each choice?
-James On Apr 27, 2010, at 11:30 AM, Thomas Mueller wrote: > Hi, > >> When would one want to use "memFS" instead of "mem" for an in-memory db? > > memFS is mainly used for testing. It uses the same algorithms as a > regular file system. Probably it needs less memory than mem. memLZF > needs even less memory because it compresses the data (which slows it > down). > > See also http://www.h2database.com/html/advanced.html#file_system > > Regards, > Thomas > > -- > 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.
