Hi Daniel

If it is supported in the JDBC interface of the database system, then two run-throughs are executed:

1st run - active: all constraints are enabled during the insertion process.

2nd run - inactive:: disabling all constraints (FK, PK and UK), inserting the rows into the database tables, reenabling the constraints.

Databases where this is not possible have the entry 'active - no choice^. The fastest run is displayed. Improvement then shows the ratio to the other run variant.

For MariaDB it means that the run with enabled constraints is 73.7% faster than the run with disabled constraints.

Hope this helps.

On Mon, 13 Sept 2021 at 04:01, Daniel Black <daniel@mariadb.org> wrote:

Hey Walter,

Thanks for sharing.

The 73.7% mariadb drop is in the query speed(?) is compared to which other measurement? An earlier MariaDB version and/or a new DBSeeder version?

On Sun, Sep 12, 2021 at 10:55 PM Walter Weinmann <walter.at.konnexions@gmail.com> wrote:
We are pleased to release version 3.0.3 of DBSeeder (https://github.com/KonnexionsGmbH/db_seeder).

DBSeeder also supports the latest version of MariaDB Server available on Docker Hub (DBMS 10.6.4-focal) and Maven Repository (JDBC 2.7.4).

_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp