Fred
Thank you for the information. By rewriting the middleware piece to use an index field, the queries are drastically improved. I mean, it is amazing the difference.
So, the middleware just keeps an vector filled (with a huge number) of objects that correspond to the index of a record based on other fields. Before sending the query to the server, we go through the vector until we find the mapping to the proper index id. Even with going through the big vector, it is a drastic improvement. It is still proof-of-concept at this point and we will be experimenting with how to implement something even faster (on the middleware end).
Thanks again for your help.
Mike
>>
Date: Fri, 9 Oct 2009 14:01:51 +0100
From: "fredt" <
fredt@...>
Subject: Re: [Hsqldb-user] Improving speed of a select query
To: "HSQLdb user discussions" <
hsqldb-user@...>
Message-ID: <984FD936975943D78766DB1BC148C3B6@BLACK>
Content-Type: text/plain; charset="iso-8859-1"
Querying should be done against an index field, otherwise each query against
a million rows may take several seconds.
You should be able to join the 30,000 row list with the 1M row table, which
will improve total time a lot.
If you post a simplified example of the tables, I can give you more specific
advice.
Fred
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Hsqldb-user mailing list
Hsqldb-user@...
https://lists.sourceforge.net/lists/listinfo/hsqldb-user
