HSQLDB Memory Limit Running with CACHED Tables



Running on linux, 64-bit kernel, sun jvm 1.6.0, what is the limit of
the total memory that HSQLDB will use for rows in memory?

From the FAQ (at http://hsqldb.org/web/hsqlFAQ.html):

"The current (1.8.0) size limit of an HSQLDB database is 8GB for all
CACHED tables, 2GB for each TEXT table and less than 2GB for all
memory tables."

But I am not sure this tells me enough about how much will HSQLDB fit
in memory.

If the machine has 8GB of physical RAM and the JVM is set to use all
of it, can HSQLDB go up to, say 6GB, for the rows in memory? This is
provided, of course, that we set the cache numbers appropriately.

Thanks.

.



Relevant Pages

  • Re: local disk based JDBC implementation
    ... my impression is that Cloudscape works like a "real" disk-based ... while HSQLDB is caching the whole dataset in memory. ... for that kind of work you may not want an embedded db engine anyway.. ...
    (comp.lang.java.programmer)
  • Re: local disk based JDBC implementation
    ... > db engine, while HSQLDB is caching the whole dataset in memory. ...
    (comp.lang.java.programmer)
  • Re: excessive paging w/ mass inserts into HSQLDB
    ... I think that HSQLDB puts everything into memory. ... You can periodically monitor the JVM ... you will begin noticing the paging. ...
    (comp.lang.java.databases)
  • Re: DBModelled Storage in JAVA
    ... I know about HSQLDB, it wil be faster than Traditional database but ... will not be as fast as i have the data in memory. ...
    (comp.lang.java.databases)
  • Web Application OutOfMemory
    ... we have been getting a number of OutOfMemory errors appearing in our web ... In one of the web applications, I have tried to get some info on memory ... I find that the total memory varies between 63MB and 48MB. ...
    (comp.lang.java.help)