[Hsqldb-developers] Performance Questions...

[Gabriel L. <ga...@bu...>]

Howdy,

I'm using the 1.7.0 release embedded in our application. Its working
really well thanx! I have two issues with it right now, first the files
on teh filesystem seem to get pretty large relatively quickly. Looking
at them in an editor they appear to be the kind of thing that would
compress really nicely. I took a quick look at the persistence code and
it looks like it would be pretty easy to compress the rows before they
get written to disk and to uncompress them when they get read. Has
anyone else looked at this? what would be the perf implications?

Second, I'm running a couple of queries that seemt to take a really long
time. I'm wondering if there is any way to get some insight into how the
engine is deciding to process the request? I'd like to see if it is
using my indexes or if there are other indexes I need to create? Can
anyone point me to the logic in the code that decides how to process a
request, I'd like to find out what the best way to create indexes is? If
I have several items in a where clause should I create compound indexes?
If this stuff is answered already somewhere sorry, please point me to
the location. 

Thanx,
=-gabe