Hi Bert, HSQLDB is fairly aggressive at using memory, to the extent that I believe it tries to keep entire tables in memory. If you decide to use HSQLDB in embedded mode, you will therefore have to give MCF memory that is consistent with your particular task, and expect to run out of memory periodically as things grow.
If you use HSQLDB as an external database, then I think you'd only need to worry about the HSQLDB instance itself. But that would certainly decrease the convenience you are looking for. Karl On Mon, Feb 2, 2015 at 1:53 PM, Bert Randolf <[email protected]> wrote: > > Hi, > > we think about running ManifoldCF on a Filesystem Database to ease > installation and reduce infrastructure costs. > Since derby is not recommended for production use the only option left > would be HSQLDB. > > Is it recommended to run ManifoldCF on HSQLDB in a production environment? > Are there any known limitations compared to postgres or mysql (besides > performance)? > > Thanks in advance, > Bert >
