dungba88 opened a new issue, #15344: URL: https://github.com/apache/lucene/issues/15344
### Description Lucene now has great [profiling support](https://github.com/apache/lucene/blob/main/lucene/sandbox/src/java/org/apache/lucene/sandbox/search/QueryProfilerIndexSearcher.java) for understanding search-time costs. It provides detailed breakdowns of time spent across sub-queries and scorers. I'm wondering if it makes sense to expand profiling support to other value-producing components, such as Lucene `DoubleValuesSource`. In Amazon Product Search, we make heavy use of this powerful dynamic expression features for search (such as filtering or scoring based on a runtime computed expression). So having a profiling for `DoubleValuesSource` could be really useful since we can track down slow ones and optimize. This could also benefit other users who rely on this feature as well. I'm happy to draft a PR and iterate. Opening this issue to gather community feedback first. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
