Re: [PR] PointInSetQuery use reverse collection to improve performance [lucene]

2025-03-28 Thread via GitHub
github-actions[bot] commented on PR #14352: URL: https://github.com/apache/lucene/pull/14352#issuecomment-2762926172 This PR has not had activity in the past 2 weeks, labeling it as stale. If the PR is waiting for review, notify the d...@lucene.apache.org list. Thank you for your contributi

Re: [PR] PointInSetQuery use reverse collection to improve performance [lucene]

2025-03-14 Thread via GitHub
hanbj commented on PR #14352: URL: https://github.com/apache/lucene/pull/14352#issuecomment-2724230306 Thank you for providing ideas. In scenarios with multiple dimensions, the internal nodes in the bkd tree can only be sorted according to a certain dimension. Different internal nodes may h

Re: [PR] PointInSetQuery use reverse collection to improve performance [lucene]

2025-03-13 Thread via GitHub
msfroh commented on PR #14352: URL: https://github.com/apache/lucene/pull/14352#issuecomment-2722703844 > Another new thought is that I believe SinglePointVisitor is unnecessary, as processing each point separately will traverse the bkd tree multiple times. MergePointVisitor will only trave

[PR] PointInSetQuery use reverse collection to improve performance [lucene]

2025-03-13 Thread via GitHub
hanbj opened a new pull request, #14352: URL: https://github.com/apache/lucene/pull/14352 ### Description Performance issues with terms number field encountered in production environments: high query time and very high CPU usage. Through analysis and localization, it was found