On Thursday, March 28, 2019 at 8:40:31 AM UTC+1, Evgenij Ryazanov wrote: > > Hello. > > Could you build a standalone test case that can be used to reproduce such > slowdown? I don't see any reasons for it. >
Hi, @Joe: based on your comments, I've built a standalone performance test using JMeter. Not only you were right, but the situation has been around for some time since 1.4.197, maybe even before. @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). I'm surprised no one ever measured H2 performance in a statistical manner. I'm even more surprised by the results... On these releases 1.2.147, 1.3.176, 1.4.196 and 1.4.199, the following scenario ran for 200 virtual users in a memory-only database: perform a complex CTE 1000 times on a indexed taxonomy database, with parametrized input. This clearly shows a drop not only on latest 1.4.199, but the drop became substantial from 1.4.197 onward. Below is a percentile graph showing that 1.2.147 (almost 9 years old!) is still the fastest H2 engine on a pure memory database... Followed by 1.3.176, then 1.4.196. Versions from 1.4.197 to 1.4.199 really came up with a new performance issue which can be felt by any of the 200 virtual users. What dramatically changed between 1.4.196 and 1.4.197? [image: h2a.png] <about:invalid#zClosurez> -- 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.
