Hi, > 50 minutes are needed to open the connection after an unexpected VM > shutdown with MVCC=TRUE, 30 seconds without this parameter.
The next version of H2 will not use MVCC when recovering, so it will no longer take 50 minutes. However, it would be still good to know why it takes so long. Also, the 30 seconds are still too long I guess. Could you send me such a database, or profile it? For the MVCC mode, it doen't need to be the whole 50 minutes; probably 10 minutes are enough to get a good picture. To profile, use java -Xrunhprof:cpu=samples,depth=32,interval=1 ... 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.
