void 🌖
banner
leloup.dev
void 🌖
@leloup.dev
Adrien Leloup
I like code, food, and when people help each other.

Tech director @whitecube.be
Building @hiker.dev
Organizing @phpxbru.com 🇧🇪
Man I know. I had my finger on the "book flight" button. The flight & hotel is still a chunk of money though. But I've been wanting to visit Japan... aaaahhh
November 14, 2025 at 3:41 PM
I know, it’s wild! Are you going?
November 14, 2025 at 1:05 PM
@jessarcher.bsky.social no doubt whatsoever
November 13, 2025 at 10:33 AM
Yep!
November 12, 2025 at 7:13 PM
Another thing, not sure if that applies for you but if you're using Docker Desktop, just don't. Use the CLI. The desktop app is so resource hungry for no reason. It made a huge difference in execution speed when I switched to CLI on our self hosted Github Actions runners.
November 12, 2025 at 7:03 PM
Yes, 100%. If you're waiting for the right moment, you'll never do it. Believe me, from experience, you'll be so thankful down the line that you took the time to set it all up now. It'll always be a bigger effort to do it later than to do it now.
November 12, 2025 at 7:01 PM
I've had the same thing happen actually! This really helped: forums.docker.com/t/mysql-slow...
MySQL Slow Performance In Docker
Hi @redsandro, everyone, I had the same problem, running mysql anormally slow in docker, and discovered that it had nothing to do with docker at all (i have pretty much the same configuration as you,...
forums.docker.com
November 12, 2025 at 6:58 PM
I will say what we do is migrate the DB before running the tests, seed some data, then export to a SQL file that we can quickly re-import on a test by test basis. That's because we're running Dusk tests and so we can't use the RefreshDatabase trait.
November 12, 2025 at 11:33 AM
Another idea is to see if you need to run all the migrations for all the databases for every test or not. Maybe there's a way to structure your parallel execution so that you don't need every database to be migrated in every case?
November 12, 2025 at 11:26 AM
I don't have anything quite that large but with 95 tables and 160 migrations, running the migrations is pretty quick and hasn't been a problem here. How long does it take to generate for you?
November 12, 2025 at 11:22 AM
I don't think there's an obvious solution for that other than trying to see if there's stuff you can remove (changes that are introduced in a migration only to be undone by another migration down the line).

Maybe artisan schema:dump if you're not already doing it.
November 12, 2025 at 11:14 AM
> Ignition returns as open source...with the same rich debugging context we collect for Performance Monitoring.

Love to read this!
November 12, 2025 at 10:45 AM
Dude I've been fighting the urge for the past few weeks as well! You got some stuff cooking already?
October 9, 2025 at 8:15 AM
Get well soon kitties! 🚑
October 8, 2025 at 1:12 PM
I'm worried as well :/
October 3, 2025 at 3:41 PM
Congrats! 🥳
October 1, 2025 at 9:56 AM