Re: [h2] Re: Recent drops in performance
Now I remember why - recursive table queries. On Sun, 5 May 2019 at 08:11, Evgenij Ryazanov wrote: > PreparedStatement re-parses such queries during each invocation. > > And we also have another known problem with CTEs: temporary views from > different statements may conflict with each other. Such views should not be > visible outside of the command. > > -- > 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 https://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
PreparedStatement re-parses such queries during each invocation. And we also have another known problem with CTEs: temporary views from different statements may conflict with each other. Such views should not be visible outside of the command. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
Its unfortunate that we are creating and destroying local temp tables for each query - since we're using a PreparedStatement, they should ideally be cached and only dropped when the connection is closed. But I remember trying to improve our CTE architecture and not having much luck. The lifecycle is rather tricky. Perhaps we should switch to just inlining CTEs at every use-site. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
org.h2.table.TableView.destroyShadowTableForRecursiveExpression (boolean, org.h2.engine.Session, org.h2.table.Table) calls org.h2.engine.Session.removeLocalTempTable (org.h2.table.Table) that calls org.h2.engine.Database.lockMeta (org.h2.engine.Session) We have a bottleneck here. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
Previous message was truncated, so check the attachment.
--
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 https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.Random;
public class CTETest {
static String[] A = { "ID", "88", "000188", "000288", "000388", "000488", "000588", "000688", "000788",
"000888", "203688", "000988", "001088", "001188", "001288", "001388", "001488", "001688", "001788",
"001888", "001988", "002088", "002188", "002288", "002488", "002588", "002688", "002788", "002888",
"002988", "003088", "003188", "003288", "003388", "003488", "003588", "003688", "003788", "004188",
"004388", "004488", "004688", "004288", "003888", "003988", "004088", "193788", "004788", "004888",
"004988", "005088", "005188", "005288", "005388", "005488", "180788", "005588", "005688", "005788",
"005888", "005988", "006088", "006188", "006288", "006388", "006488", "006588", "006688", "006788",
"006888", "006988", "007088", "007188", "007288", "189488", "007388", "007488", "007588", "007888",
"007988", "008288", "008388", "008488", "008588", "008688", "008788", "008088", "008188", "007688",
"007788", "00", "008988", "009088", "009188", "009288", "203788", "009388", "009488", "009588",
"009688", "009788", "180888", "009888", "009988", "183888", "010088", "010188", "010288", "010388",
"010488", "010588", "010688", "010788", "010888", "010988", "011088", "011188", "011288", "011388",
"182988", "011488", "011588", "011688", "011788", "011888", "011988", "012088", "012188", "012288",
"012388", "012488", "012588", "012688", "012788", "012888", "012988", "013088", "013288", "013388",
"013488", "013588", "013688", "181288", "181388", "013788", "013888", "181488", "181588", "013988",
"181688", "014088", "189688", "189788", "189888", "189988", "190188", "190288", "190388", "190488",
"190588", "190688", "190788", "190888", "190988", "191088", "191188", "191288", "191388", "191488",
"191588", "191688", "191788", "191888", "194188", "194288", "194388", "194588", "194688", "014288",
"014388", "014588", "014688", "014888", "014988", "015088", "015288", "015388", "015488", "015688",
"015888", "015988", "016088", "016188", "016288", "016388", "016488", "016588", "016688", "016788",
"016888", "016988", "017088", "017188", "192088", "017288", "181788", "017388", "017488", "017588",
"017688", "017788", "192188", "017888", "184088", "017988", "183488", "194888", "018088", "018188",
"018288", "018388", "018488", "194988", "018688", "018788", "01", "018988", "019088", "019188",
"019288", "195088", "019388", "195188", "181888", "019488", "019588", "019688", "195288", "019788",
"019888", "019988", "020088", "020188", "020288", "020388", "020488", "192288", "020588", "020688",
"020788", "020888", "020988", "021088", "195488", "021188", "195588", "021288", "021388", "021488",
"021588", "181988", "021688", "021788", "021888", "021988", "195688", "022088", "022188", "022288",
"022388", "022488", "022588", "022688", "184388", "022788", "022888", "022988", "023088", "023188",
"195788", "023288", "023388", "023488", "023588", "023788", "023888", "023988", "024088", "024188",
"024288", "024388", "024488", "024588", "024688", "024788", "024888", "025088", "025188", "195888",
"025288", "024988", "025388", "025488", "025788", "025888", "025988", "026188", "026288", "026388",
"182088", "026488", "026588", "192888", "026688", "026788", "026888", "026988", "192588", "025588",
"025688", "026088", "027088", "027188", "027288", "027388", "027488", "027588", "027688", "027788",
"027888", "027988", "028088", "028188", "184688", "028288", "195988", "028388", "028488", "028588",
"028688", "028788", "02", "028988", "029088", "029188", "029288", "029388", "029488", "029588",
"182188", "029688", "029788", "029888", "029988", "030088", "196088", "030188", "030288", "030388",
"030488", "030588", "030688", "030788", "030888", "030988", "031088", "031188", "031288", "031388",
"031488", "031588", "031688", "031788", "031888", "031988", "032088", "032188", "032288", "032388",
"032488", "032588", "032688", "032788", "032888",
Re: [h2] Re: Recent drops in performance
I run a git bisect. https://github.com/h2database/h2database/commit/7977b90bd13e9088a3dc1ed8b60efb2699e97724 is the first slow commit. It was merged in https://github.com/h2database/h2database/pull/640 -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
With 200 threads both 1.4.197 and 1.4.199 work about 6–7 times slower than 1.4.196. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
I used the same query as in you test case. I can repeat the test with 200 threads. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
Are you doing 1 times a CTE or just a simple SELECT? 200 users concurrency is needed else indeed some versions will feel similar. I also built a ramp up of 4 seconds. It's a steep ramp up but allows to measure how h2 recovers from sudden increase of traffic. I would like to emphasise that from a statistical point of view, having percentiles graphs with close match from 1.2.47 to 1.4.196 means the code and architecture are equivalent. 1.4.197 included a sudden change. I'll track it down using git bisect. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
what do your test results look like with 200 threads? I'm guessing Christian's test case is mostly testing contention on hot locks. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
I wrote and run a simple 4-thread test with 4 connections and 4 prepared statements with values from population.csv. I tested all values distributed between these threads (All) and also 10,000 randomly selected values per thread (Random). Measured times in seconds are average times between multiple runs. They include time taken to open the database. These measures are approximate. All Random 1.4.196 PageStore 2.5 11.9 1.4.196 MVStore 2.3 14.0 1.4.197 PageStore 2.9 22.6 1.4.197 MVStore 2.8 25.5 1.4.199 PageStore 2.5 11.7 1.4.199 MVStore 2.28 10.4 1.4.198 is definitely slower (this version includes some temporary bugfixes, but such slowness is still surprising), but 1.4.199 is not. Of course, this test is not equal to original test case that runs these queries through the web interface I guess. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
Correct -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
You would need to build a thread engine sending these queries through jdbc. Not impossible. I used JMeter as it's a java product already available I use on daily basis. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
No. It's the init.sql that populates the db. JMeter only opens the pre-existing populated db, and then indeed run CTE for all IDs in population.csv. I wish it could have been in a shape of an automated testscase, but it's not. This one highlights the performance issue only. I will try to do some git bisects next week to find the root cause of 197 drops vs 196 -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
>From reading the .jmx file, it looks like JMeter will populate the database from the CSV file, and then run a query (specified inside the JMX file) from multiple simultaneous threads. Should be able to run a profiler on the H2 instance while the JMeter test is running. Not as nice as standalone code, I know. I'll run it on Monday and see what the Netbeans profiler shows. On Sat, 4 May 2019 at 12:44, Evgenij Ryazanov wrote: > We need code that can be profiled directly with any suitable tool. But not > the third-party environment that does something with the web interface of > H2. > > It looks like population.csv contains the identities that should be passed > to the provided query, but I'm not sure. > > -- > 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 https://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
We need code that can be profiled directly with any suitable tool. But not the third-party environment that does something with the web interface of H2. It looks like population.csv contains the identities that should be passed to the provided query, but I'm not sure. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
@Evgenij looks like the way it works is to open the .jmx file in Apache JMeter https://jmeter.apache.org/ and run the test plan -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
We need a standalone test case (Java/SQL only) for further investigation. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
This script is to initialize the db and test only once the CTE query. If you just do this with one user and no volume, the difference of performance is difficult to notice. You might notice something if your system is under heavy cpu or io load. The measurement of CTE is done by the jmx file using jmeter and volume (20 queries on a population using CSV parametrization). It's done on a db with data (from taxnum.csv). So if you just do the CTE once in a while you won't notice anything. There really is a difference of performance, you need statistical analysis with volume, hence the use of JMeter. Hope this clarifies. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
Hello. Your cte.sql contains runscript from 'init.sql'; Do you measure performance of the query or performance of database population with data? I don't see any noticeable differences in execution time of the query itself between 1.4.196 and 1.4.199 in both PageStore and MVStore databases with their default settings. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
Hi, I moved away from memory database to pure embedded database, using pagestore format. I stick to CTE, as it was supported for the releases used inside comparison scope, and CTE is slowish to allow comparison of graphs. DDL and DDQ were too fast for the graphs to be differentiated. I've posted my JMeter code at github: https://github.com/cmichon/h2lander "In the end, there can be only one H2 release" :-D If you wish to reproduce this, you'll need JMeter 5.1.1 with following plugins: - jp@gc - Response Times Percentiles - jp@gc - Active Threads Over Time In order to run this load test, you need to initialize a local db first, using the init.sql file provided. You can use the cte.sql in order to build a standalone java testcase. I preferred using JMeter in order to add some concurrency, allowing to stress H2 enough to have decent graphs. You can find the jtl results and HTML reports as 7-zip archives on github. Jtl file can be reloaded inside the listeners of JMeter. If you do not know how JMeter works, either use the HTML report or look at the picture below. Results are unchanged: H2-1.4.196 was on par with H2-1.2 and H2-1.3, but last 3 releases of H2 have worse timings, especially 1.4.197. Here's the graph: I keep the TCP analysis aside for now. Rgds Christian On Wednesday, May 1, 2019 at 9:19:20 AM UTC+2, Christian MICHON wrote: > > Yes in memory only for now. > > I can move it to embedded files and tcp as well. > > What I saw is a sudden drop of performance between 196 and 197. That drop > was halved and partially recovered in 198 and 199. > > But it's still, for that particular use case (CTE), too slow compared to > older versions. > > I managed my refactoring in JMeter to remove jdbc connection pool, as this > was the issue between sessions and DDL use case. I also reverted to a CTE > use case. > > I'll share this on github after my analysis with embedded and tcp. For tcp > I'll need to use a separate machine. > > Rgds > Christian > > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
Yes in memory only for now. I can move it to embedded files and tcp as well. What I saw is a sudden drop of performance between 196 and 197. That drop was halved and partially recovered in 198 and 199. But it's still, for that particular use case (CTE), too slow compared to older versions. I managed my refactoring in JMeter to remove jdbc connection pool, as this was the issue between sessions and DDL use case. I also reverted to a CTE use case. I'll share this on github after my analysis with embedded and tcp. For tcp I'll need to use a separate machine. Rgds Christian -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
So you're testing in-memory only? Hmmm, then your results are kind of what I expect. If you're testing in-memory, you are testing the cost of our parsing and storage management layers. Which have become more expensive as we have become more sophisticated. If you really care about in-memory performance, then the right answer is ConcurrentHashMap, not H2 :-) So what we are really interested in, is how good we are at dealing with the limited bandwidth available when we talking to a disk storage subsystem. That said, if we can find any ways to shave off overhead in the in-memory case, that will be still be a good thing, On Tue, 30 Apr 2019 at 07:05, Christian MICHON wrote: > I'll do that and keep you posted > > -- > 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 https://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
I'll do that and keep you posted -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
Please keep in mind, that even for in-memory database, pgstore or mvstore are still very much in use. So it looks like apples-to-oranges comparison indeed. To make them comparable I would switch to pgstore use in 1.4 versions, by explicitly specifying MVSTORE=FALSE in url. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
jdbc:h2:mem:tsn it's a memory db. Keep in mind that the standalone test case is a load test. You'll need JMeter to run it and other versions of H2 to compare via individual runs. I'll get this ready soon On Monday, April 29, 2019 at 3:28:22 AM UTC+2, andre...@gmail.com wrote: > > I wonder how your URL looks like and whether it is apples to oranges > comparison, because default settings have changed between those versions, > most notably default storage engine was pagestore in older versions vs > mvsore in recent ones. That alone can have big performance impact. > > In any case, we still need your standalone test case > > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
I wonder how your URL looks like and whether it is apples to oranges comparison, because default settings have changed between those versions, most notably default storage engine was pagestore in older versions vs mvsore in recent ones. That alone can have big performance impact. In any case, we still need your standalone test case -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
On Friday, April 26, 2019 at 4:30:49 PM UTC+2, Noel Grandin wrote: > > > > On 2019/04/26 4:15 PM, Christian MICHON wrote: > > @Evgenij : it's not rocket science to build such scenario, if you need > such performance test scenario, I'll share it on > > github (it's not confidential). > > > > Yes please, let's see the test case. > Gladly. The first testcase relied on big csv files, there were no thinktime, and it was relying on CTE. I will have to fix the 2nd testcase as it doesn't work with 1.4.198. Once it's ready I'll create a small repo on github for your reference. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Re: Recent drops in performance
On 2019/04/26 4:15 PM, Christian MICHON wrote: @Evgenij : it's not rocket science to build such scenario, if you need such performance test scenario, I'll share it on github (it's not confidential). Yes please, let's see the test case. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
