We are using H2 in embedded mode on constrained hardware with read/write files. The data model is straightforward, the datasets are moderate in size, and the queries not particularly complex.
The problem is that from time to time a query takes much longer to execute, like 20-100x longer. I expect some internal H2 housekeeping may be causing this (index rebuilding, defrag, compaction or other). Any ideas what tunings we might consider to limit this type of non-deterministic behavior? We have played with transaction log and cache sizing with little effect. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/nzcFTB2M12oJ. 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.
