Track down performance regression on BulkPostings [LUCENE-2890]
Open
affects-version:Bulk Postings branch
legacy-jira-fix-version:6.0
legacy-jira-priority:Major
type:task
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Spinoff from #3797 - since we are seeing performance regression on BulkPostings especially for advance/jump calls we should track that those down rather sooner than later.
---
Migrated from [LUCENE-2890](https://issues.apache.org/jira/browse/LUCENE-2890) by Simon Willnauer (@s1monw), updated May 09 2016
Linked issues:
- #3797
Contributor guide
Research direction
The issue names BulkPostings and its advance/jump calls; start by reading linked issue #3797 and locating that implementation and any existing performance measurements. Done means the regression is reproduced, its cause is identified, and the relevant performance check confirms the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100