Batch virtual calls from DefaultBulkScorer#scoreRange
Open
type:enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
### Description
While working on performance issue for OpenSearch customer workload, I could notice significant virtual call overhead coming from `DefaultBulkScorer#scoreRange`. Although it was observed primarily for scroll queries, the optimization could benefit many other queries.
Contributor guide
Research direction
Start at DefaultBulkScorer#scoreRange and trace how its virtual calls occur during scoring, especially for scroll queries. Compare the current behavior with the proposed batched approach and verify that scoring results remain unchanged while virtual-call overhead is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100