monty please confirm that the test should use commit 23afec6966a in branch bb-10.7-selectivity. I ask because that commit (although the last one) is marked as being from Mon Nov 1 12:34:24 2021 +0200. This could however be an artefact from git workflow.

Please also add any details that are missing in this ticket. I take from our conversation in slack, that there are no special settings required in my.cnf. So I will run 10.7 and 10.7-selectivity with the same my.cnf. I'll do ANALYZE TABLE <tablename> after loading and before running the queries. Does this need some special options?

Once you are ready, please assign this Jira ticket back to me. I'd like to run the benchmarks over the weekend, so this is kind of urgent.

You should use the last commit in 10.7-selectivity (don't use bb-10.7-selectivity, that is an old one)
Otherwise the ticket is ok

I have added data for 6 different DBT3 runs:

• SF10 and SF30 not using histograms
• SF10, SF30, SF50 and SF100 using histograms

The histograms were enforced using ANALYZE TABLE ... PERSISTENT FOR ALL with setting analyze_sample_percentage = 0 (automatically chosing a sample percentage). Even when histograms were used, some warmup effect was visible. That means: even when using the same execution plan, subsequent runs were faster then the first one.

The database versions under test were

• vanilla MariaDB 10.7.3
• git branch 10.7-selectivity, commit a523568eab5

both built locally using the same compiler and build script.

Result:

MariaDB 10.7.3 is almost always faster. There are a few queries that 10.7-selectivity executes 10% or more faster (marked green in attached spreed sheet). But also some queries, notably Q6, Q8, Q12 and Q20 that 10.7-selectivity executes 10% or more (much more) slower. Those are marked red.

The RAR file contains the complete results, especially the EXPLAIN EXTENDED plans.

Attachments:

MDEV-28434.ods spread sheet with high level overview of data. MDEV-28434.rar archive with complete results. Subdir res01 is for 10.7.3, res02 for 10.7-selectivity.

followup ticket MDEV-29929