Linking to a table in a separate db is a creative solution. Thomas, thank you
for the suggestion. It may be useful to me.
The intended usage of my table is several hundred million rows.
The columns are one double value plus a primary key plus 3 foreign keys.
There is an index for each foreign key plus one composite index of 3 foreign
keys.
Is this within the scope that H2 is designed for?
I will want to delete 20 million rows occasionally.
The deletion does not seem possible at this time.
I will try the settings suggested for bulk imports.
I have just 5 million rows at present and H2 is not coping.
I’m grateful for the replies by four people – I was despondent and you have
cheered me up
From: Thomas Mueller-6 [via H2 Database]
Sent: Thursday, July 05, 2012 6:40 PM
To: jarradk
Subject: Re: Performance: DROP TABLE very slow on large tables
Hi,
What you could do is create the large table in a separate database, and link it
using "create linked table". Instead of dropping the table, you could then just
delete the database.
Regards,
Thomas
On Thursday, July 5, 2012, Steve McLeod wrote:
I've also experienced this slowness when dropping a large table. I spent a
considerable amount of time with the H2 source code trying to find a way to
speed things up, but alas it turns out not to be an easy task with the current
data store.
On Thursday, 5 July 2012 13:35:17 UTC+4, wburzyns wrote:
I did a similar experiment. My table consists of 3 columns (BIGINT NOT
NULL DEFAULT NEXT VALUE FOR GLOBAL_SEQ PRIMARY KEY, BLOB, BLOB) an
currrently has over 11*10^6 rows (total DB size is over 17 GB).
Dropping of this table was ugly slow - I interrupted it after 15
minutes, cannot afford waiting for several hours like jarradk :) I
noticed that during the proccess the DB files have grown in size by
several GBs. Additionally 'pageStore: Transaction log could not be
truncated' appeared in the trace file.
I'm on latest-greatest version of H2.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/h2-database/-/VD5FkrFQnEkJ.
To post to this group, send email to <a href="javascript:_e({},
'cvml', '[email protected]');"
target="_blank">h2-database@....
To unsubscribe from this group, send email to <a href="javascript:_e({},
'cvml', 'h2-database%[email protected]');"
target="_blank">h2-database+unsubscribe@....
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
--------------------------------------------------------------------------------
If you reply to this email, your message will be added to the discussion below:
http://h2-database.66688.n3.nabble.com/Performance-DROP-TABLE-very-slow-on-large-tables-tp2885986p4024553.html
To unsubscribe from Performance: DROP TABLE very slow on large tables, click
here.
NAML
--
View this message in context:
http://h2-database.66688.n3.nabble.com/Performance-DROP-TABLE-very-slow-on-large-tables-tp2885986p4024563.html
Sent from the H2 Database mailing list archive at Nabble.com.
--
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.
