Hi Thomas, Thank you for your very fast reactivity on this issue. Version 1.2.144 fills the gap, I can say now the H2 is a perfect alternative to HSQL !
We had memory issues with 1.1 versions and that explains the CACHE_SIZE=0. I removed it know, and it seems to work well, even if recover takes about 30 seconds. I explain it by the fact that we have a lot of links in our database and index building must be a big job. Thanx again for your precious help. Best regards from South of France, Pierre -----Message d'origine----- De : h2-database@googlegroups.com [mailto:h2-datab...@googlegroups.com] De la part de Thomas Mueller Envoyé : dimanche 17 octobre 2010 12:03 À : h2-database@googlegroups.com Objet : Re: Very slow database connection after server crash Hi, With version 1.2.144 the performance problem opening a database with MVCC=TRUE should be fixed. There is a problem in your database URL: you are using CACHE_SIZE=0. This is really bad for performance. Please use at least CACHE_SIZE=1024, or better the default value. Using CACHE_SIZE=0 explains why opening the database can take 30 seconds. 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 h2-datab...@googlegroups.com. To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com. 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 h2-datab...@googlegroups.com. To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
