Closed mocobeta closed 2 years ago
exitable
makes sense to me as there isn't much we can do when queries hit a timeout from a benchmark perspective
TaskQPS baseline StdDevQPS exitable_directory_reader StdDev Pct diff p-value BrowseMonthTaxoFacets 166.54 (13.2%) 80.06 (17.7%) -51.9% ( -73% - -24%) 0.000
Egads! Maybe open a followon issue in Lucene Jira (or GitHub issues soon maybe!) to improve performance of ExitableDirectoryReader
for these pure-browse cases? That's far more impact than I expectd!
and I'll add you as committer on this project too.
Aha! You are already :) Thanks!
Thanks for merging, I'll look at the javascript part - this will be much harder for me.
I'll look at the javascript part - this will be much harder for me.
Hmm what is the javascript part?
I'll look at the javascript part - this will be much harder for me.
Hmm what is the javascript part?
I guess we need a graph in https://home.apache.org/~mikemccand/lucenebench/ to make it vital and some javascript is needed for that? But maybe I'm missing something...
Oh! Yes that would be wonderful, and is indeed trickier. I suggest opening a new issue to "Measure ExitableDirectoryReader overhead in nightly benchmarks"?
168
Instead of
timeout
parameter (#171), I addedexitable
boolean option this time. Whenexitable=True
, the directory reader is wrapped by ExitableDirectoryReader, where the timeout is-1
(this is interpreted to Long.MAX_VALUE inQueryTimeoutImpl
constructor).Usage (
localrun.py
)A sampled result (with
-source wikimedium1m
)