From: Baris Kazar
Sent: Tuesday, October 5, 2021 3:56 PM
To: Adrien Grand ; Lucene Users Mailing List
; Baris Kazar
Subject: Re: org.apache.lucene.search.BooleanWeight.bulkScorer() and
BulkScorer.score()
Hi Adrien,-
Thanks for taking a look at it and sure, that will be very nice to fix
: Tuesday, October 5, 2021 3:18 PM
To: Lucene Users Mailing List
Cc: Baris Kazar
Subject: Re: org.apache.lucene.search.BooleanWeight.bulkScorer() and
BulkScorer.score()
Hmm we should fix these access$ accessors by fixing the visibility of some
fields.
These breakdowns do not necessarily signal
gt; Next: BulkScorer.score() with its call tree and time spent:
>
>
>
> BulkScorer.score()
> -->> Weight$DefaultBulkScorer.score()
> -->>-->> Weight$DefaultBulkScorer.scoreAll()
> -->>-->>-->> WANDScorer$1.nextDoc()
> -->>-->>-->&
.score()
-->> Weight$DefaultBulkScorer.score()
-->>-->> Weight$DefaultBulkScorer.scoreAll()
-->>-->>-->> WANDScorer$1.nextDoc()
-->>-->>-->>-->> WANDScorer$1.advance()
-->>-->>-->>-->>-->> WANDScorer.access$300() (constitutes %65 of
Bul
: Adrien Grand
Sent: Saturday, October 2, 2021 1:44:40 AM
To: Lucene Users Mailing List
Cc: Baris Kazar
Subject: Re: org.apache.lucene.search.BooleanWeight.bulkScorer() and
BulkScorer.score()
Is your profiler reporting inclusive or exclusive costs for each function? Ie.
does it exclude time
Is your profiler reporting inclusive or exclusive costs for each function?
Ie. does it exclude time spent in functions that are called within a
function? I'm asking because it makes total sense for IndexSearcher#search
to spend most of its time is BulkScorer#score, which coordinates the whole
match
