postgres-drizzle got slow
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.2k
- Forks
- 1.8k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 6
Description
I was looking at these nice examples comparing latency of different sql db modules:
- https://postgres-drizzle.vercel.app
- https://postgres-prisma.vercel.app
- https://postgres-kysely.vercel.app
I noticed that prisma and kyseley are both very fast on second request (~500ms for the first request then ~5ms for kyseley and ~25 for prisma). However, the drizzle example stays at 250ms+.
Is there a config difference with the deployment?
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the three deployed examples at postgres-drizzle.vercel.app, postgres-prisma.vercel.app, and postgres-kysely.vercel.app, focusing on deployment and database configuration. Confirm the repeated-request latency difference and identify the relevant configuration or entry point; done means the Drizzle example's behavior is explained and any confirmed configuration issue is corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, typescript
- Domain
- databases, devops, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100