Not sure if I would choose H2 for a 2TB database. I don't think it has
been tested too well with databases of that size. It would probably need
a lot of RAM.
I'd be inclined to try smaller files rather than a single 2TB file. For
instance backing up, or recovery of corrupt databases will be much
better handled.
But it really depends on your use case. If it is just to do some number
crunching, then a single file might be fine.
On 3/12/2013 1:14 PM, James Chan wrote:
I'm curious about the performance, wish to have your comments, thanks.
If my database will grow to 2TB, should I keep all data in only one
file? or split the file into smaller pieces? (if 1GB per file, than
there will be 2048 files). Or there's no big difference between these
two types?
--
You received this message because you are subscribed to the Google
Groups "H2 Database" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
