Hey dear Prisma team, I am currently testing prisma against typeorm with PostgreSQL. I am trying to use nested writes for Prisma. With local DB the query takes around 4s. When I run the same query with remote DB on AWS then it takes around 90s. Would you have any hint on why is it taking so long with remote DB. See more details on stackoverflow. Let me know if you need more details.

You can try setting

DEBUG="*"

in your environment. Then you can look at timestamps on print messages in cloudwatch to see what is taking so long. I’m doing this right now. Prisma seems to be adding 2-3 seconds to performing simple queries.

Add the

nApi

preview feature to decrease this.

@Ryan I am using prisma versioN: 3.1.1, according to this release statement the napi query enginer should be used by default

The latency shouldn’t be 90 seconds, as for the above logs that @Mischa has posted,

nApi

isn’t enabled.

@Ryan Those aren't my logs 🙂 Let me create an example for you

As for me I am trying to test out prisma 3 but I have a small issue https://github.com/prisma/prisma/issues/9520 will post more results

I've run this with debug=* but haven't seen anything suspicious there. You can check the output here. Also there is an example repo now that demonstrates the problem.

I just did some simple testing of my own on lambda/aurora: https://prisma.slack.com/archives/CCWDULGUW/p1633011980135600

@Ryan Any hints on what can be an issue here?

I will test this and get back to you. Also do you run the query locally pointing to the remote DB or is it on the deployed app?

I run it locally pointing to the remote DB

And is the DB in the same region as you are?

@Ryan No its' not. But as mentioned above running the type of writing operation with typeorm works within 3 seconds. Based on this I don't think it's something to do with network