Skip to content

[TASK] Speed up MySQL functional database resets - #741

Open
wouter90 wants to merge 1 commit into
TYPO3:mainfrom
wouter90:optimize-mysql-functional-reset
Open

[TASK] Speed up MySQL functional database resets#741
wouter90 wants to merge 1 commit into
TYPO3:mainfrom
wouter90:optimize-mysql-functional-reset

Conversation

@wouter90

Copy link
Copy Markdown
Contributor

Functional test cleanup currently truncates every touched MySQL or MariaDB table. TRUNCATE is expensive DDL even for tables without an auto-increment column, where no sequence state needs to be restored.

Delete rows from touched tables without auto-increment instead, while retaining TRUNCATE for tables whose counter changed. MySQL may omit the current counter for populated auto-increment tables, so inspect column metadata before selecting DELETE in that ambiguous case.

For Extbase RelationTest, this reduces MariaDB 10.4 runtime from about 63.3 to 57.3 seconds and MySQL 8.4 runtime from 112.1 to 100.1 seconds. The complete MariaDB functional suite passes with 12,523 tests and 73,326 assertions.

Functional test cleanup currently truncates every touched MySQL or MariaDB table. TRUNCATE is expensive DDL even for tables without an auto-increment column, where no sequence state needs to be restored.

Delete rows from touched tables without auto-increment instead, while retaining TRUNCATE for tables whose counter changed. MySQL may omit the current counter for populated auto-increment tables, so inspect column metadata before selecting DELETE in that ambiguous case.

For Extbase RelationTest, this reduces MariaDB 10.4 runtime from about 63.3 to 57.3 seconds and MySQL 8.4 runtime from 112.1 to 100.1 seconds. The complete MariaDB functional suite passes with 12,523 tests and 73,326 assertions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant