spring-projects / spring-projects/spring-boot
Improve startup performance of DevTools by starting fileSystemWatcher async
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
While debugging I noticed that ClassPathFileSystemWatcher#afterPropertiesSet spends a lot of time launching the fileSystemWatcher.
This could be optimized by starting the fileSystemWatcher async (similar to how this is done with spring.jpa.bootstrap) or maybe utilizing the Watcher Thread for the initial FileSystem work.
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 at ClassPathFileSystemWatcher#afterPropertiesSet and compare the asynchronous startup approach used by spring.jpa.bootstrap. Determine how the fileSystemWatcher can start without blocking DevTools startup, while preserving initial file-system work and watcher behavior. Done means startup no longer spends most of its time launching the watcher.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100