Skip to content

storage: default MySQL snapshot PK-range parallelism to off#37879

Open
peterdukelarsen wants to merge 1 commit into
MaterializeInc:mainfrom
peterdukelarsen:pl/mysql-snapshot-parallelism-default-off
Open

storage: default MySQL snapshot PK-range parallelism to off#37879
peterdukelarsen wants to merge 1 commit into
MaterializeInc:mainfrom
peterdukelarsen:pl/mysql-snapshot-parallelism-default-off

Conversation

@peterdukelarsen

Copy link
Copy Markdown
Contributor

Motivation

Scale tests are showing that for large MySQL tables this change does not improve performance. I tested on a 1B row table and while the test is still running, the old version is on pace to complete faster than the parallelized implementation.

Description

Defaults MySQL parallelism to be off. It does not disable the new parallelism-supporting structure.

Verification

Flip the mysql_source_snapshot_parallelism dyncfg default from true to
false, so new deployments use the legacy single-worker-per-table
snapshot unless the flag is enabled. Parallel PK-range snapshotting
stays available behind the flag and is now rolled out selectively via
LaunchDarkly rather than being on everywhere by default.

CI continues to run with the flag enabled through the mzcompose default
system parameters, so the parallel path keeps its test coverage.
@peterdukelarsen
peterdukelarsen requested a review from a team as a code owner July 24, 2026 21:48
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