Hello, when running

db seed

locally to my production database, it finishes in about 5-10 seconds. When I run it on Github Actions with pretty much the exact same settings it takes almost 50+ seconds. It must be some sort of connection stuff, or maybe lower number of cores, or poor connection, but is there any way i can start to debug it?

Depending on what you find out from Prisma team, you could always self host a github runner https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners This would allow you to beef up the environment that’s running your

db seed

command. Whether it be more CPU power, more ram, etc.

Yeah I was thinking about that. It feels a bit off though, I don't think 1 core or less ram should effect the speed on the computer that is running the queries right? Usually the database is what is slow Especially, on a free runner, you can build docker images and do npm install pretty quickly so it can't be that slow

that does seem slow