Applying migrations to MariaDB (running directly on macOS) unreasonably slow

Bug description

We have user reports of unusually slow migrations with MariaDB on OSX. We did investigate and found the following timings for working with 100 migrations:

Linux

• migrate deploy 22s
• migrate dev 1m30s
• single sql command to db, 6ms

Mac

• migrate deploy 3m25s
• migrate dev 10m34s
• single sql command to db 28ms

Napkin math: deploy issues 3 mysql commands under the hood, so 3 x 28ms X 100 migrations ~ 10s but what we see is > 600s on mac

How to reproduce

Expected behavior

No response

Prisma information

Environment & setup

• OS: OSX 12.01
• Database: MariaDB 10.6.4
• Node.js version: v17.0.1

Prisma Version

prisma                  : 3.4.0
@prisma/client          : 3.4.0
Current platform        : darwin
Query Engine (Node-API) : libquery-engine 1c9fdaa9e2319b814822d6dbfd0a69e1fcc13a85 (at node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine        : migration-engine-cli 1c9fdaa9e2319b814822d6dbfd0a69e1fcc13a85 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core 1c9fdaa9e2319b814822d6dbfd0a69e1fcc13a85 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt 1c9fdaa9e2319b814822d6dbfd0a69e1fcc13a85 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : 1c9fdaa9e2319b814822d6dbfd0a69e1fcc13a85
Studio                  : 0.438.0

[amcjen]

Moved over to a MariaDB Docker instance and indeed it is much much faster than before. We’ll move ahead with this approach–thank you for all your help, glad migrations are back to about 10 seconds instead of 15 minutes! 🙌

[floelhoeffel]

That’s quite the speed bump 😅 Glad that using docker is working for you.