@GetMapping for GET requests in Spring Boot - Performance & Optimization

Performance: @GetMapping for GET requests

MEDIUM IMPACT

This affects server response time and client perceived loading speed by handling HTTP GET requests efficiently.

Handling HTTP GET requests in a Spring Boot REST controller

Spring Boot

@GetMapping("/data")
public CompletableFuture<String> getData() {
    return CompletableFuture.supplyAsync(() -> {
        // Simulate async processing
        try {
            Thread.sleep(5000);
        } catch (InterruptedException e) {
            e.printStackTrace();
        }
        return "Data";
    });
}

Handles processing asynchronously, freeing server threads to handle other requests and improving response concurrency.

📈 Performance GainNon-blocking server threads improve throughput and reduce LCP under load.

Handling HTTP GET requests in a Spring Boot REST controller

Spring Boot

@GetMapping("/data")
public String getData() {
    // Heavy synchronous processing
    try {
        Thread.sleep(5000); // Simulate delay
    } catch (InterruptedException e) {
        e.printStackTrace();
    }
    return "Data";
}

Blocking the thread with heavy synchronous processing delays response, increasing server response time and slowing page load.

📉 Performance CostBlocks server thread for 5 seconds, increasing LCP and causing slow user experience.

Performance Comparison

Pattern	Server Thread Usage	Response Delay	Impact on LCP	Verdict
Synchronous blocking @GetMapping	Blocks thread during processing	High delay (e.g., 5s)	Increases LCP significantly	[X] Bad
Asynchronous @GetMapping with CompletableFuture	Non-blocking, frees threads	Response delayed but server handles concurrency better	Improves LCP under load	[OK] Good

Rendering Pipeline

The @GetMapping method processes the GET request on the server, then sends the response to the browser which triggers rendering.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing when synchronous/blocking code delays response

Core Web Vital Affected

LCP

This affects server response time and client perceived loading speed by handling HTTP GET requests efficiently.

Optimization Tips

1Avoid blocking operations inside @GetMapping methods to reduce server response time.

2Use asynchronous processing or caching to improve concurrency and speed.

3Monitor server response times in DevTools Network tab to catch delays early.

Performance Quiz - 3 Questions

What is the main performance issue with a synchronous @GetMapping method that blocks the thread?

A It causes browser rendering errors

B It delays server response, increasing LCP

C It reduces network bandwidth

D It increases CSS paint time

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the time taken for the GET request to complete.

What to look for: Look for long waiting (TTFB) times indicating server delay; shorter times mean better performance.