Hi Ivaylo, It would be MUCH easier if you just post java code here instead. BTW, table population with auto-commit on, no batches, and embedded data instead of prepared statement is not the fastest way of doing this, so when you say "the execution times for inserting the data were similar", it realy means "similarly terrible".
Going back to SELECT, my results for "SELECT * FROM TableB" execution time: v. 1.4.197: PgStore: 2.3 sec. MVStore: 5.1 sec. v. 1.4.198 SNAPSHOT, built from commit ac05e08c8aafe6d8680ec09b9b2ee371355ffb4c, which you mentioned (With latest snapshot results are similar): PgStore: 2.4 sec. MVStore: 1.2 sec. It seems like there is absolutely nothing special about your test case, and results are consistent with what I posted above for some 7 column 300000 rows table of my own making. Most likely, when you was measuring time with some SQL client (Squirl ?), it does not pick up driver, you expect. Why not just run your test as standalone java program? And please build latest clean jar, by following instructions, because one you posted is a bit weird, even if you just look at it's directory listing. The bottom line is: in 1.4.197 this select ~ 2 times slower with MVStore vs. PgStore, whereas in latest version it's 2 times faster. Best of luck! Andrei -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
