P
Prisma6mo ago
imoby

Queries 200-400ms slower after migrating to queryCompiler (6.10.1)

I've recently migrated to the new queryCompiler and even after noticing mention of the new performance improvements in 6.10.1 I am still seeing a big degration to all my queries, at least 200 to sometimes like 600ms slower. I'm running on serverless environment. I"m using Postgres and I have views setup and some of my queries are using transactions but after switching back to the non queryCompiler things are back to how they were before. Is there a starting point on how I can debug what's going on here, I'm not seeing any improvement here.
3 Replies
Prisma AI Help
Prisma AI Help6mo ago
You decided to hold for human wisdom. We'll chime in soon! Meanwhile, #ask-ai is there if you need a quick second opinion.
Nurul
Nurul6mo ago
Can you enable query logging and check if the same underlying SQL is generated in both cases?
Logging | Prisma Documentation
Learn how to configure Prisma Client to log the raw SQL queries it sends to the database and other information.
imoby
imobyOP6mo ago
Yes I can check still having the same issue, I'm seeing sometimes even 1 - 1.5 seconds delay. on average its about 400ms longer but sometimes way more for context, a cold start on my current service (everything exactly same, except switching to prisma 6.10.1 and using new queryCompiler): - current: max 2.2 seconds with cold start - new (6.10.1 QC): 3.4+ seconds theres definitely a huge bottleneck somewhere. the query itself is showing exactly same @Nurul @Nurul any update on this? this seems like a pretty critical blocker potentially for some folks on serverless envs. I'm comparing the query and its the same. however looking at the logs I can see that the duration is a lot longer. Even on the latest 6.11.1. Have you all done any testing in serverless lambda environments?

Did you find this page helpful?