Prisma Client usage in NestJS - Performance & Optimization

Performance: Prisma Client usage

MEDIUM IMPACT

This affects server response time and database query efficiency, impacting how fast data is fetched and sent to the frontend.

Fetching related data with Prisma Client

NestJS

const users = await prisma.user.findMany({ include: { posts: true } });

Fetches users and their posts in a single query, reducing database calls.

📈 Performance GainSingle database query regardless of number of users, significantly faster response.

Fetching related data with Prisma Client

NestJS

const users = await prisma.user.findMany();
for (const user of users) {
  user.posts = await prisma.post.findMany({ where: { authorId: user.id } });
}

This triggers one query per user, causing many database calls and slowing response time.

📉 Performance CostTriggers N database queries for N users, increasing server response time linearly.

Performance Comparison

Pattern	Database Queries	Server Response Time	Network Payload	Verdict
N+1 Query Pattern	Multiple queries (N+1)	High due to many DB calls	Larger due to repeated data	[X] Bad
Single Query with Include	Single optimized query	Low and consistent	Smaller and efficient	[OK] Good

Rendering Pipeline

Prisma Client usage affects the server-side data fetching stage before the frontend rendering begins. Slow queries delay data availability, causing slower initial paint and interaction readiness.

→Server Data Fetching

→Network Response

→Frontend Rendering

⚠️ BottleneckServer Data Fetching due to inefficient or multiple database queries.

Core Web Vital Affected

INP

This affects server response time and database query efficiency, impacting how fast data is fetched and sent to the frontend.

Optimization Tips

1Avoid running database queries inside loops to prevent N+1 query problems.

2Use Prisma's include or select options to fetch related data in one query.

3Monitor API response times to catch slow Prisma queries impacting user experience.

Performance Quiz - 3 Questions

What is the main performance problem with running a database query inside a loop for each user?

A It causes many database queries, increasing server response time.

B It reduces network payload size.

C It improves caching automatically.

D It speeds up frontend rendering.

DevTools: Network and Performance panels

How to check: Use Network panel to monitor API response times and number of requests; use Performance panel to see server response blocking time.

What to look for: Look for fewer API calls with faster response times indicating efficient Prisma queries.