Hi, See the change log (http://www.h2database.com/html/changelog.html) , there are too many fixes and improvement from version 1.2.135 , even a new experimental SHUTDOWN DEFRAG.
El 21/09/10 22:22, sheng escribió: > The major issue that we are encountering is the H2 DB performance > degraded as the size of the DB grown over time. In order to regain the > H2 performance our operation team needs to remove the database > completely and let the application rebuild the database from scratch, > two times a week. Please describe your use case and what operations are the most degraded and some metric of such degradation. If you can tell us what's you database size , connection URL, OS and fileSystem ? I have running databases with monthly maintenance (financial apps) with an acceptable sustained performance. Have you done any test with a newer H2 version ? > So I am investigating this issue from two direction, first, I am > looking for a solution like AUTOVACUUM in Postgres that allows zero > human intervention to compact the database at runtime. > I noticed there is a priority 2 task as follow in the 1.3.x release > that might be an alternative for AUTOVACUUM. > # Compact databases without having to close the database (vacuum). > > I am wondering is there a date for the release? or a patch that I can > apply immediately for addressing this issue? As far as I know, not yet. Regards, Dario. -- 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.
