P
Prisma•3mo ago
imoby

New queryCompiler with postgres adapter in AWS lambda poor performance

I've been following the prisma queryCompiler and now that its been more GA I'm seeing that none of the performance issues have been addressed here. Not sure if nextjs is a first class citizen here but I'm hosting my stuff on serverless framework on AWS lambda functions, and I've seen a huge decrease in performance. At a minimum I'm seeing like 1-2 seconds additional latency. Sometimes even more with just changing the bare mimimum to make this run in the new query compiler 
generator client {
  provider        = "prisma-client-js"
  engineType      = "client"
  previewFeatures = ["views", "relationJoins"]
}
generator client {
  provider        = "prisma-client-js"
  engineType      = "client"
  previewFeatures = ["views", "relationJoins"]
}
Anyone else run into this?
3 Replies
Prisma AI Help
Prisma AI Help•3mo ago
You chose to debug with a human. They'll tinker with your query soon. If you get curious meanwhile, hop into #ask-ai for a quick spin!
Nurul
Nurul•3mo ago
Can you check if you get the same behaviour if you use the prisma-client generator instead of prisma-client-js?
imoby
imobyOP•3mo ago
yes I just switched to using the prisma-client too and same issue. My query that normally takes 3 seconds including cold start time now takes 5.8 seconds. across the board all my queries have had performance hits. I was looking for some of the benefits of lambda size reduction but this performance is going to be a dealbreaker for me @Nurul

Did you find this page helpful?