GoogleCloudPlatform / GoogleCloudPlatform/spring-cloud-gcp

Compatibility with Spring Boot 4.1.1 : Doubling of CPU Usage

Open
#4,616 2 comments 0 reactions 0 assignees View on GitHub
priority: p3 type: bug
Dominant language
Java
Stars
551
Forks
349
Avg merge
1d 13h
Merged PRs (30d)
14

Description

After upgrading our project to Spring Boot `4.1.1`, we observed that the CPU usage has consistently doubled compared to the previous version. This increase is stable and persists over time, with the CPU utilization remaining at approximately twice the normal level. Importantly, the CPU is not experiencing spikes or temporary surges; rather, it is operating at a steady, elevated level following the library update. This change impacts system performance and resource allocation.
We had to roll back to Spring Boot `4.1.0`.

Here are, our main deps :
```
com.google.cloud:libraries-bom
com.google.cloud:spring-cloud-gcp-dependencies
org.springframework.boot:spring-boot-starter-aspectj
org.springframework.boot:spring-boot-starter
org.springframework.boot:spring-boot-starter-web
org.springframework.boot:spring-boot-starter-jetty
org.springframework.boot:spring-boot-starter-actuator
org.springframework.boot:spring-boot-starter-data-jpa
org.springframework.boot:spring-boot-starter-validation
org.springframework.boot:spring-boot-starter-cache
org.springframework.boot:spring-boot-starter-integration
org.springframework.data:spring-data-envers
com.google.cloud:spring-cloud-gcp-starter-trace
com.google.cloud:spring-cloud-gcp-starter-pubsub
org.springframework.boot:spring-boot-starter-security
org.springframework.boot:spring-boot-starter-oauth2-resource-server
org.springframework.boot:spring-boot-starter-liquibase
com.google.cloud:google-cloud-spanner-jdbc
com.google.cloud:google-cloud-spanner-hibernate-dialect
com.google.cloudspannerecosystem:liquibase-spanner
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported CPU comparison with the listed dependencies on Spring Boot 4.1.0 and 4.1.1, then profile the application to identify what changed. The issue is done when the source of the sustained increase is isolated and a verified fix or regression report demonstrates normal CPU usage on the affected version.

Written by the indexing model from the issue text.

Assessment

Tech stack
google-cloud, java, spring-boot
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.