Link to trace file: https://drive.google.com/open?id=0B7fRq__lUQbCRXJIM2NCVVdpZGM
This is the trace from running one test class with four test methods. Serious DDL and catalog queries going on. Run with JDBC URL options ";AUTO_SERVER=true;mv_store=false;mvcc=false;TRACE_LEVEL_FILE=3;". Timing comparison: SQL Server 3' 02", H2 (with no trace file): 5' 19". (Not good!) On Monday, July 27, 2015 at 11:53:57 PM UTC-7, Noel Grandin wrote: > > > > On 2015-07-28 01:42 AM, Wes Clark wrote: > > I build a new jar (twice), and reran the offending suite, and the > performance problem was still evident. Should I get > > another trace? > > Yeah, let's see what it looks like now. > -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
