Hi Mikkel,

I wonder about the query performance, we have similar configuration
with only ~1M records in a single table.
and the client works with LIMIT 1000.
and some of the queries can take up to 2 minutes.
What do yuo mean by "an offset on a unique BIGINT"

BTW:
We are working in server mode with two threads one that populate the
DB and other that read the data and some times write Metadata
information to another table.
Regards
Dror


On Jun 11, 8:28 am, Mikkel Kamstrup Erlandsen
<[email protected]> wrote:
> 2009/6/8 Lucky Luke <[email protected]>:
>
>
>
> > Hello,
>
> > I just found out about H2, and I was wondering how well it handles
> > large databases (e.g. 50Gb - 100Gb in size). We have a database that
> > has 2 dozen lookup tables that are small, and about half a dozen
> > tables that are potentially very large with several million rows.
>
> > Some just contain integer data, some contain varchar values for log
> > data. Data is mostly just inserted, and every now and then queried
> > with result sets of up to 2500 records.
>
> > Is this something that H2 would handle well, or is it not designed to
> > deal with large databases?
>
> We are running a setup with ~8M records in a single table and H2
> doesn't complain at all. We iterate over the entire table with client
> side paging, ie. with LIMIT 500 and with an offset on a unique BIGINT
> column and can read about 5000 records/s this way last I checked. At
> one point we had some left outer joins in our paging query (so I'd say
> avoid those) but that gave quite a performance hit - I don't recall
> the exact numbers though.
>
> I am a happy camper at least :-)
>
> --
> Cheers,
> Mikkel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to