We have recently rolled out H2 as the store for a pretty big cache in a web app. The database is about 2.5GB, and has probably around 1 million rows, in a single table. Some of those rows are big, we have around 30,000 lobs. The problem we've seen, is that memory usage in the server goes crazy. The server has 8GB of RAM, and the JVM is allocated a maximum of of 4GB. Eventually the JVM process ends up taking more than 10GB of RAM, making the server go into swap and killing performance. Since the JVM is limited to 4GB, I'm assuming that the extra memory is native resource memory. We're still not sure this is related to H2, it's one of the most significant changes we rolled out. Has anyone had issues like this? Is it reasonable to handle a database this big with 4GB of RAM?
Any insight would be appreciated. Andres -- 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.
