Prisma:query SELECT "public"."Link"."id", "public"."Link"."emailProtected", "public"."Link"."enableNotification", "public"."Link"."password" FROM "public"."Link" WHERE ("public"."Link"."id" = $1 AND 1=1) LIMIT $2 OFFSET $3 ✓ Compiled /api/views in 97ms (207 modules) Next.js 14 + Vercel Postgres + Prisma 5.6.x How to reproduce Parallelize queries with Promise.all not sure if that will help tho.Pass documentVersionId in request so the "Get Pages" query is not dependent on any other query.Connect Link and DocumentVersion models directly.Perhaps I can even use Prisma Accelerate for some of the more static queries. I think there's potential for optimization. it still takes about ~8s for prisma queries. Ignoring track analytics and send email, which will be offloaded to a background job and are not prisma queries. However, they this function takes ultra long to execute: ~12s. I have an api route that executes a series of Prisma queries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |