Thanks Andrei. Not sure though why the file would grow as it is 500MB already (.mv.db) and the front-end app does not update, insert or sends DDL. It is pretty much read-only, except one or 2 small tables updated for stats purposes. Are you saying deserialized data take up much more space ? I would have thought the opposite.
We are trying to right-size a (Linux) docker container running h2 along with a tomcat app, on Kubernetes so RAM allocation is up to us. While 512MB cache may seem a waste, it is immaterial when running on cloud resources. On Friday, December 28, 2018 at 12:23:08 PM UTC-5, Andrei Tokar wrote: > > First of all, do not be surprized if your file will grow well beyond yor > data size, so 500Mb should not be your guideline. As far as caching raw > file data, OS will do a good job if memory is plentiful. H2 caches > deserialized data pages, and it is definitely a waste try to cache all of > that data, even infrequently used, or not at all. If performance is you > concern, and you’ve got plenty of RAM, try incrementaly increase heap size > (default cache size will increase accordingly), until you reach the point > of diminishing return. -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
