spring-projects / spring-projects/spring-boot
Reduce GC pressure of ConditionMessage creation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
The creation of condition messages performs a reasonable amount of string concatenation that's contributing to GC pressure during startup. Without Actuator and --debug, the messages will never actually be read. It might be interesting to investigate computing the messages lazily. It may not be straightforward as the message String is currently used in hashCode and equals implementations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing ConditionMessage creation during startup and examine how its message String is used by hashCode and equals. Determine whether lazy message computation can avoid unnecessary concatenation while preserving those semantics, then validate the effect on startup allocation and GC behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100