Hi Noel, hi Andrei, thanks for your explanations around the compact procedures!
I will try to play with the WRITE_DELAY parameter and see if that improves the database filesize behaviour. Data removal is executed in one transaction per table. It is not easily possible to change the application in order to use batch inserts. So I tried to use SHUTDOWN COMPACT when the CHUNK_FILL_RATE drops below a given threshold and/or filesize exceeds a given threshold. The downside is that compaction takes up to 10 minutes when the database is large (e.g. 50GB). This is a downtime of the application which I want to minimize. The reason I am contacting you is that MVStore database are growing much much faster than the old PageStore databases, no matter if autocompaction is enabled or not. This is a big downside for me so I would be happy if you can improve this at some point. Anyhow, from my point of view H2 is a very good database especially in embedded context! Thanks! Ulrich -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/d2bf3ba1-7008-4f6d-97a9-12a684812f75n%40googlegroups.com.
