Hi, > I'm worried about last change log notice of CACHE_SIZE using half of > JVM -Xmx.
Do you mean this entry?: "When opening an existing database, the cache size is set to at most half the amount of memory available for the virtual machine (Runtime.getRuntime().maxMemory()), even if the cache size setting stored in the database is larger. Setting the cache size in the database URL or explicitly using SET CACHE_SIZE overrides this value (even if larger than the physical memory)." The "half of JVM" only applies if the cache size defined in the cache_size setting is *larger* than that. The reason for this change is: sometimes I get databases with the cache_size set very large. As the cache_size setting is persisted (in the database) this is problematic (slow performance, sometimes even out of memory). The change in version 1.2.136 is just a safeguard against forgetting to reset this value. Maybe it would be better to not persist the cache_size setting in the database itself (not sure). 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.
