Here are the H2 database settings: H2 Database Settingsname <file:///C:/tmp/index.html#> (hide) <file:///C:/tmp/index.html#>value <file:///C:/tmp/index.html#> (hide) <file:///C:/tmp/index.html#>CREATE_BUILD187DB_CLOSE_DELAY-1 CACHE_SIZE131072info.BUILD_ID187info.VERSION_MAJOR1info.VERSION_MINOR4 info.VERSION1.4.187 (2015-04-10)property.java.runtime.version1.7.0_45-b18 property.java.vm.nameJava HotSpot(TM) 64-Bit Server VMproperty.java.vendorOracle Corporationproperty.os.nameWindows 7property.os.archamd64property.os.version 6.1property.sun.os.patch.levelService Pack 1property.file.separator\ property.path.separator;property.line.separator property.user.countryUSproperty.user.languageenproperty.user.variant property.file.encodingwindows-1252EXCLUSIVEFALSEMODEOracleMULTI_THREADED0 MVCCTRUEQUERY_TIMEOUT0RETENTION_TIME0LOG2ALIAS_COLUMN_NAMEfalseANALYZE_AUTO 2000ANALYZE_SAMPLE10000COMPRESSfalseDATABASE_TO_UPPERtrueDB_CLOSE_ON_EXIT trueDEFAULT_CONNECTIONfalseDEFAULT_ESCAPE\DEFAULT_TABLE_ENGINE<null> DEFRAG_ALWAYSfalseDROP_RESTRICTtrueEARLY_FILTERfalse ESTIMATED_FUNCTION_TABLE_ROWS1000FUNCTIONS_IN_SCHEMAtrueLARGE_TRANSACTIONS trueLOB_TIMEOUT300000MAX_COMPACT_COUNT2147483647MAX_COMPACT_TIME200 MAX_QUERY_TIMEOUT0MV_STOREtrueNESTED_JOINStrueOPTIMIZE_DISTINCTtrue OPTIMIZE_EVALUATABLE_SUBQUERIEStrueOPTIMIZE_INSERT_FROM_SELECTtrue OPTIMIZE_IN_LISTtrueOPTIMIZE_IN_SELECTtrueOPTIMIZE_IS_NULLtrueOPTIMIZE_OR trueOPTIMIZE_TWO_EQUALStrueOPTIMIZE_UPDATEtruePAGE_STORE_INTERNAL_COUNTfalse PAGE_STORE_MAX_GROWTH131072PAGE_STORE_TRIMtrueQUERY_CACHE_SIZE8 RECOMPILE_ALWAYSfalseRECONNECT_CHECK_DELAY200REUSE_SPACEtrueROWIDtrue SELECT_FOR_UPDATE_MVCCtrueSHARE_LINKED_CONNECTIONStrue <file:///C:/tmp/index.html#TOP> The URL we use is totally generic: jdbc:h2:mem:px
Attached is the log file from our test suite with the thread dumps in line. I hope these are useful for you. On Friday, June 12, 2015 at 10:03:37 AM UTC-7, Wes Clark wrote: > > We are testing the latest H2 version (from a recent nightly build, > actually) in place of a rather ancient but serviceable version 1.2. We are > seeing performance degradation of at least a factor of 6. We have suites > of test. I can supply you with comparison timings, but for example a suite > that takes 20 minutes on the old H2 is timing out after 3 hours. If we > don't need MVCC for a suite, we could run it without it. Will that recover > the lost time? (That's an experiment I will run later.) We want to take > advantage of MVCC (and DBStore) for some integration suites where we hope > it will prevent deadlocks. Let me know if you need more details, or if you > can respond with general comments about expected performance. > -- 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/d/optout.
h2_thread_dumps.7z
Description: application/7z-compressed
