The settings are from SELECT * FROM INFORMATION_SCHEMA.SETTING. On Monday, June 15, 2015 at 11:42:57 AM UTC-7, Wes Clark wrote: > > We also may explicitly set ";lock_timeout=10000". > > On Monday, June 15, 2015 at 11:34:24 AM UTC-7, Wes Clark wrote: >> >> Here are the H2 database settings: >> H2 Database Settingsname >> (hide) value >> (hide) CREATE_BUILD187DB_CLOSE_DELAY-1CACHE_SIZE131072info.BUILD_ID187 >> info.VERSION_MAJOR1info.VERSION_MINOR4info.VERSION1.4.187 (2015-04-10) >> property.java.runtime.version1.7.0_45-b18property.java.vm.nameJava >> HotSpot(TM) 64-Bit Server VMproperty.java.vendorOracle Corporation >> property.os.nameWindows 7property.os.archamd64property.os.version6.1 >> property.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_NAMEfalse >> ANALYZE_AUTO2000ANALYZE_SAMPLE10000COMPRESSfalseDATABASE_TO_UPPERtrue >> DB_CLOSE_ON_EXITtrueDEFAULT_CONNECTIONfalseDEFAULT_ESCAPE\ >> DEFAULT_TABLE_ENGINE<null>DEFRAG_ALWAYSfalseDROP_RESTRICTtrueEARLY_FILTER >> falseESTIMATED_FUNCTION_TABLE_ROWS1000FUNCTIONS_IN_SCHEMAtrue >> LARGE_TRANSACTIONStrueLOB_TIMEOUT300000MAX_COMPACT_COUNT2147483647 >> MAX_COMPACT_TIME200MAX_QUERY_TIMEOUT0MV_STOREtrueNESTED_JOINStrue >> OPTIMIZE_DISTINCTtrueOPTIMIZE_EVALUATABLE_SUBQUERIEStrue >> OPTIMIZE_INSERT_FROM_SELECTtrueOPTIMIZE_IN_LISTtrueOPTIMIZE_IN_SELECTtrue >> OPTIMIZE_IS_NULLtrueOPTIMIZE_ORtrueOPTIMIZE_TWO_EQUALStrueOPTIMIZE_UPDATE >> truePAGE_STORE_INTERNAL_COUNTfalsePAGE_STORE_MAX_GROWTH131072 >> PAGE_STORE_TRIMtrueQUERY_CACHE_SIZE8RECOMPILE_ALWAYSfalse >> RECONNECT_CHECK_DELAY200REUSE_SPACEtrueROWIDtrueSELECT_FOR_UPDATE_MVCC >> trueSHARE_LINKED_CONNECTIONStrue >> 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.
