[Improvement] Improve metrics performance by cache Thread info reporter
- Dominant language
- Java
- Stars
- 454
- Forks
- 172
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 5
Description
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [X] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues.
### What would you like to be improved?
### How should we improve?
_No response_
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
Contributor guide
Research direction
The issue provides only an image and no file, test, or entry point. Start by locating the metrics code and the Thread info reporter, then establish how its performance is measured. Done means the reporter's Thread information remains correct while metrics collection avoids unnecessary repeated work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100