New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Share TermsEnum if possible while applying DV updates [LUCENE-8602] #9648
Comments
ASF subversion and git services (migrated from JIRA) Commit d08e2d4 in lucene-solr's branch refs/heads/master from @s1monw LUCENE-8602: Share TermsEnum if possible while applying DV updates Today we pull a new terms enum when we apply DV updates even though the |
ASF subversion and git services (migrated from JIRA) Commit 01ad36d in lucene-solr's branch refs/heads/branch_7x from @s1monw LUCENE-8602: Share TermsEnum if possible while applying DV updates Today we pull a new terms enum when we apply DV updates even though the |
ASF subversion and git services (migrated from JIRA) Commit d08e2d4 in lucene-solr's branch refs/heads/jira/http2 from @s1monw LUCENE-8602: Share TermsEnum if possible while applying DV updates Today we pull a new terms enum when we apply DV updates even though the |
ASF subversion and git services (migrated from JIRA) Commit 4272c63 in lucene-solr's branch refs/heads/master from @s1monw #9654: Extract utility class to iterate over terms docs Today we re-implement the same algorithm in various places |
ASF subversion and git services (migrated from JIRA) Commit 8f4e4a4 in lucene-solr's branch refs/heads/branch_7x from @s1monw #9654: Extract utility class to iterate over terms docs Today we re-implement the same algorithm in various places |
Today we pull a new terms enum when we apply DV updates even though the
field stays the same which is the common case. Benchmarking this on a
larger term dictionary with a significant number of updates shows a
2x improvement in performance.
Migrated from LUCENE-8602 by Simon Willnauer (@s1monw), resolved Dec 11 2018
Pull requests: apache/lucene-solr#523
The text was updated successfully, but these errors were encountered: