1) Ensure that all Indexes and constraints are turned off yes, faster
2) Reduce the commit size. As far as I can see you create one very large commit over all records. Instead, commit as per 1k or 4k records or so. i tried 1k and 10k per commit, not much different, sometimes 1k is slower than 10k. thanks Andreas On Sunday 14 January 2024 at 01:21:36 UTC+8 [email protected] wrote: > 1xk mean i can insert 10-15 thousand records to h2 per second, thanks > > On Friday 12 January 2024 at 16:41:03 UTC+8 Andreas Reichel wrote: > >> Forgot one: >> >> try multi threading, e. g. populating one prepared statement while >> another is executed/written. >> Not guaranteed if this really will be faster though. >> >> On Fri, 2024-01-12 at 15:38 +0700, Andreas Reichel wrote: >> >> Greetings. >> >> On Fri, 2024-01-12 at 00:17 -0800, [email protected] wrote: >> >> hi. I am running AMD 3900x with 128GB ram and a nvme ssd. Now i can >> insert 1xk record per seconds, which is very fast. But how can I make is 10 >> times more? what hardware can do that? >> >> >> 1) Ensure that all Indexes and constraints are turned off >> 2) Reduce the commit size. As far as I can see you create one very large >> commit over all records. Instead, commit as per 1k or 4k records or so. >> 3) Ensure that your filesystem does not do COW or compression. >> 4) use RAID and ensure that there is ZERO waitIO or swapping >> >> What exactly does "1xk" mean? >> >> If you are really serious about loading speed you will end up with Oracle >> Loader. Not that I am promoting this shit, but in reality it is the fastest >> way for pumping data into a DB. >> >> Best regards >> Andreas >> >> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/0d855987-55f3-45ea-bca3-4cf3390f9a08n%40googlegroups.com.
