CRUD with Prisma in NestJS - Performance & Optimization

Performance: CRUD with Prisma

MEDIUM IMPACT

This concept affects server response time and database query efficiency, impacting how fast the page can load or update data.

Fetching all records with Prisma in a NestJS app

NestJS

async findAll(page = 1, limit = 10) {
  return await this.prisma.user.findMany({
    skip: (page - 1) * limit,
    take: limit
  });
}

Limits data fetched per request, reducing server load and response time.

📈 Performance GainFaster response, lower memory use, better LCP

Fetching all records with Prisma in a NestJS app

NestJS

async findAll() {
  return await this.prisma.user.findMany();
}

Fetching all records without pagination can cause large data loads, increasing response time and memory use.

📉 Performance CostBlocks server response longer as data size grows, increasing LCP delay

Performance Comparison

Pattern	Database Queries	Server Response Time	Network Payload	Verdict
Fetch all without pagination	1 large query	High due to large data	Large JSON payload	[X] Bad
Fetch with pagination	1 small query	Low and predictable	Small JSON payload	[OK] Good
Update with read then update	2 queries	Higher latency	Minimal payload	[X] Bad
Update with single query	1 query	Lower latency	Minimal payload	[OK] Good
Delete with read then delete	2 queries	Higher latency	Minimal payload	[X] Bad
Delete with single query	1 query	Lower latency	Minimal payload	[OK] Good

Rendering Pipeline

Prisma CRUD operations run on the server before the page renders. Slow queries delay server response, which delays the browser receiving data to paint the page.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing due to database query time

Core Web Vital Affected

LCP

This concept affects server response time and database query efficiency, impacting how fast the page can load or update data.

Optimization Tips

1Limit data fetched with pagination to reduce server load and network payload.

2Use single queries for update and delete to minimize database round trips.

3Avoid fetching unnecessary data to improve server response and page load speed.

Performance Quiz - 3 Questions

What is a performance downside of fetching all records without pagination in Prisma?

A It reduces server response time by fetching all data at once.

B It can cause large data loads, increasing server response time and slowing page load.

C It decreases network payload size.

D It improves browser rendering speed.

DevTools: Network

How to check: Open DevTools, go to Network tab, perform CRUD action, and observe request timing and payload size.

What to look for: Look for long server response times or large JSON payloads indicating inefficient queries.