spring-projects / spring-projects/spring-boot
Optimize startup time: Make Actuator features lazy
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
If the Actuator context and all its features were only available after the app had finished starting up and was ready to serve traffic for business requests, it might not matter a lot of the time, especially in dev mode. Benchmarks show that it might be worth it (you save 700ms on a fast machine, out of a Petclinic startup time of 3-4s).
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 reproducing the Petclinic startup benchmark and reviewing how the Actuator context and features participate in application startup. Define the startup lifecycle point at which Actuator should become available, then compare the result with the reported 700ms saving. Done means the behavior is validated without delaying business traffic readiness.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, observability-sre, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100