Why configuration matters in Spring Boot - Performance Evidence

Performance: Why configuration matters

MEDIUM IMPACT

Configuration affects application startup time, resource usage, and runtime responsiveness by controlling how components load and behave.

Loading unnecessary beans and features by default

Spring Boot

spring.main.lazy-initialization=true
# Beans load only when first used

Delays bean creation until needed, reducing startup time and memory use.

📈 Performance Gainstartup time reduced by 30-50%, less memory used initially

Loading unnecessary beans and features by default

Spring Boot

spring.main.lazy-initialization=false
# All beans load eagerly at startup

Eager loading creates many objects and runs initialization code even if not needed, slowing startup.

📉 Performance Costblocks startup for 500ms+ depending on app size

Performance Comparison

Pattern	Startup Time	Memory Usage	CPU Load	Verdict
Eager bean loading	High (slow startup)	High	Moderate	[X] Bad
Lazy bean loading	Low (fast startup)	Low	Low	[OK] Good
Verbose logging (DEBUG)	Moderate	Moderate	High	[X] Bad
Info logging level	Low	Low	Low	[OK] Good

Rendering Pipeline

Configuration controls which components load and when, affecting the JVM startup, bean initialization, and runtime execution flow.

→Application Startup

→Bean Initialization

→Runtime Execution

⚠️ BottleneckApplication Startup due to eager bean loading and unnecessary feature activation

Optimization Tips

1Enable lazy initialization to speed up startup.

2Set logging level to INFO or higher to reduce overhead.

3Disable unused features to save memory and CPU.

Performance Quiz - 3 Questions

How does enabling lazy initialization in Spring Boot affect startup performance?

A It reduces startup time by delaying bean creation until needed.

B It increases startup time by loading all beans eagerly.

C It has no effect on startup time.

D It disables bean creation entirely.

DevTools: Spring Boot Actuator and JVM Profilers

How to check: Enable Actuator endpoints to monitor startup metrics; use JVM profiler to check bean initialization time and CPU usage.

What to look for: Look for long startup phases, high memory allocation during startup, and excessive CPU during logging.

Practice

1. Why is configuration important in a Spring Boot application?

easy

A. It allows changing app behavior without modifying the code.

B. It makes the app run faster by skipping code.

C. It automatically fixes bugs in the code.

D. It prevents the app from starting without internet.

Solution

1. Step 1: Understand the role of configuration

   Configuration controls how the app behaves without changing the source code.

2. Step 2: Identify the benefit in Spring Boot

   Spring Boot uses configuration files to adjust settings easily for different environments.

3. Final Answer:

   It allows changing app behavior without modifying the code. -> Option A

4. Quick Check:

   Configuration changes behavior without code edits [OK]

Hint: Think: config changes settings, not code [OK]

Common Mistakes:

• Confusing configuration with code changes
• Believing configuration speeds up app runtime
• Assuming configuration fixes bugs automatically

2. Which of the following is the correct way to specify a property in Spring Boot's application.properties file?

easy

A. server port = 8080

B. server-port: 8080

C. server.port=8080

D. serverPort=8080

Solution

1. Step 1: Recall Spring Boot property syntax

   Spring Boot uses key=value pairs in application.properties files.

2. Step 2: Match the correct syntax

   The correct syntax uses dots to separate words and equals sign to assign values, like server.port=8080.

3. Final Answer:

   server.port=8080 -> Option C

4. Quick Check:

   Properties use dot notation and equals sign [OK]

Hint: Properties use dot notation and equals sign [OK]

Common Mistakes:

• Using colon instead of equals sign
• Using camelCase instead of dot notation
• Adding spaces around equals sign

3. Given the following application.properties content:

spring.profiles.active=dev
server.port=9090

What will be the server port when running the app with the dev profile?

medium

A. 9090 (from properties file)

B. 8080 (default port)

C. Random port assigned at runtime

D. Application will fail to start

Solution

1. Step 1: Identify active profile and property

   The active profile is set to dev, and server.port=9090 is defined.

2. Step 2: Understand profile effect on configuration

   Since server.port is set in the active profile, the app uses port 9090.

3. Final Answer:

   9090 (from properties file) -> Option A

4. Quick Check:

   Active profile sets server.port to 9090 [OK]

Hint: Active profile properties override defaults [OK]

Common Mistakes:

• Assuming default port 8080 always applies
• Thinking profile disables server port setting
• Believing app fails without explicit port

4. You have two configuration files: application.properties and application-prod.properties. You want to run the app with the prod profile but the app still uses settings from application.properties. What is the likely cause?

medium

A. Spring Boot does not support multiple configuration files.

B. The application-prod.properties file is missing a required property.

C. The app needs to be restarted twice to apply profiles.

D. The spring.profiles.active property is not set to prod.

Solution

1. Step 1: Check profile activation

   Spring Boot uses spring.profiles.active to select which profile config to load.

2. Step 2: Identify cause of fallback

   If spring.profiles.active is not set to prod, the app uses default application.properties.

3. Final Answer:

   The spring.profiles.active property is not set to prod. -> Option D

4. Quick Check:

   Profile must be activated to load its config [OK]

Hint: Activate profile with spring.profiles.active [OK]

Common Mistakes:

• Assuming file presence auto-activates profile
• Thinking missing properties cause fallback
• Believing multiple config files are unsupported

5. You want to have different database URLs for dev and prod environments in Spring Boot. Which approach correctly manages this using configuration?

hard

A. Hardcode both URLs in the main code and use if-else to select at runtime.

B. Create application-dev.properties and application-prod.properties with respective URLs, then set spring.profiles.active accordingly.

C. Use environment variables only and ignore Spring Boot profiles.

D. Put both URLs in application.properties separated by commas.

Solution

1. Step 1: Understand profile-based configuration

   Spring Boot supports multiple config files for different profiles to separate environment settings.

2. Step 2: Apply correct method for environment URLs

   Creating application-dev.properties and application-prod.properties with URLs and activating profiles is the standard way.

3. Final Answer:

   Create application-dev.properties and application-prod.properties with respective URLs, then set spring.profiles.active accordingly. -> Option B

4. Quick Check:

   Profiles separate environment configs cleanly [OK]

Hint: Use profile-specific properties files for environments [OK]

Common Mistakes:

• Hardcoding URLs in code instead of config
• Ignoring profiles and mixing URLs in one file
• Using environment variables without profiles