Hi, > What I mean is that the amount of memory consumed at any time by dbm (even > in Embedded mode) should respect an "upper bound" or at least knowable and > predictable.
It is, if you specify it in the connection setting (A). However if you don't (B), and it is set in the database, then there are two cases: - you do want to use the previous setting - you forgot that it was set previously The "automatic limit" only applies to (B). > if we can > know what's the used value ! You can. But the point is, if you do want to use an explicit value, then you need to set it each time you open the database. > Why not let this value to be dynamically adjusted based on the > available memory in the JVM conservatively ? That's what the automatic mechanism does. > Thus if, on the dbm could use idle memory. That's already available: http://h2database.com/html/features.html#cache_settings 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.
