@Around advice for full control in Spring Boot - Performance & Optimization

Performance: @Around advice for full control

MEDIUM IMPACT

This affects the runtime execution speed and responsiveness of Spring Boot applications by intercepting method calls.

Controlling method execution with @Around advice

Spring Boot

@Around("execution(* com.example..*(..))")
public Object lightweightAdvice(ProceedingJoinPoint pjp) throws Throwable {
  // minimal pre-processing
  Object result = pjp.proceed();
  // minimal post-processing
  return result;
}

Minimal logic avoids blocking and keeps method interception fast, preserving app responsiveness.

📈 Performance GainReduces overhead to near zero, avoiding added latency per method call.

Controlling method execution with @Around advice

Spring Boot

@Around("execution(* com.example..*(..))")
public Object heavyAdvice(ProceedingJoinPoint pjp) throws Throwable {
  // heavy processing before
  Thread.sleep(100); // simulate delay
  Object result = pjp.proceed();
  // heavy processing after
  Thread.sleep(100); // simulate delay
  return result;
}

Heavy processing or blocking calls inside @Around advice delay every intercepted method call, increasing response time.

📉 Performance CostAdds 200ms delay per method call intercepted, increasing latency and reducing throughput.

Performance Comparison

Pattern	Method Interception Overhead	Thread Blocking	Latency Impact	Verdict
Heavy processing in @Around advice	High (every method call)	Yes (Thread.sleep)	High latency per call	[X] Bad
Lightweight @Around advice	Low (minimal code)	No	Minimal latency	[OK] Good

Rendering Pipeline

The @Around advice intercepts method calls before and after execution, adding extra steps in the call stack.

→Method Invocation

→Application Thread Execution

⚠️ BottleneckHeavy or blocking code inside advice increases method execution time and thread blocking.

Optimization Tips

1Avoid heavy or blocking code inside @Around advice to prevent slowing method calls.

2Use @Around advice sparingly and only on necessary methods to reduce overhead.

3Profile advice execution time with Java Flight Recorder to detect performance bottlenecks.

Performance Quiz - 3 Questions

What is the main performance risk of using heavy processing inside @Around advice?

A It improves application startup time.

B It reduces bundle size.

C It increases method call latency and blocks threads.

D It decreases memory usage.

DevTools: Spring Boot Actuator + Java Flight Recorder

How to check: Enable Actuator metrics and record method execution times with Java Flight Recorder to profile advice overhead.

What to look for: Look for increased method execution times and thread blocking during advice execution.